https://coptr.digipres.org/api.php?action=feedcontributions&user=Lfaria&feedformat=atomCOPTR - User contributions [en-gb]2024-03-28T20:50:01ZUser contributionsMediaWiki 1.35.14https://coptr.digipres.org/index.php?title=Db-preservation-toolkit&diff=3265Db-preservation-toolkit2018-08-16T09:26:09Z<p>Lfaria: </p>
<hr />
<div><!-- Use the structure provided in this template, do not change it! --><br />
<br />
{{Infobox_tool<br />
|name=db-preservation-toolkit<br />
|purpose=Enables conversion between database formats or dumping from live database systems for the purposes of preservation.<br />
<!-- |image=image.png --><br />
|homepage=https://www.database-preservation.com<br />
|license=LGPL v3<br />
|platforms=Platform independent - Java<br />
}}<br />
<br />
<br />
<!-- Add one ore more categories to describe the function of the tool. Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). The following are common category examples, remove those that don't apply --><br />
[[Category:File Format Migration]]<br />
<br />
<br />
<!-- Add relevant categories to describe the content type that the tool addresses. Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. The following are common category examples, remove those that don't apply --><br />
[[Category:Database]]<br />
<br />
== Description == <br />
The Database Preservation Toolkit allows conversion between Database formats, including connection to live systems, for purposes of digitally preserving databases. The toolkit allows conversion of live or backed-up databases into preservation formats such as SIARD, a XML-based format created for the purpose of database preservation. The toolkit also allows conversion of the preservation formats back into live systems to allow the full functionality of databases.<br />
<br />
The Database Preservation Toolkit supports the following Database Management Systems:<br />
* MySQL/MariaDB<br />
* PostgreSQL<br />
* Oracle<br />
* Microsoft SQL Server<br />
* Microsoft Access<br />
* And other databases (using JDBC)<br />
<br />
Database Preservation Toolkit can convert any of the above DBMS to the following preservation formats:<br />
* SIARD 1<br />
* SIARD 2<br />
* SIARD DK<br />
<br />
The Database Preservation Toolkit is also capable of loading preserved databases into any of the above DBMS.<br />
<br />
== User Experiences ==<br />
<!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. --><br />
<br />
* https://zenodo.org/record/1171715<br />
* https://zenodo.org/record/1173099<br />
<br />
<br />
== Development Activity ==<br />
Code is being actively developed at [https://github.com/keeps/db-preservation-toolkit Database Preservation Toolkit GitHub repository].<br />
<br />
<br />
=== Release Feed ===<br />
<br />
https://github.com/keeps/db-preservation-toolkit/releases <br />
<br />
=== Activity Feed===<br />
<br />
https://github.com/keeps/db-preservation-toolkit/commits/master<br />
<br />
<br />
<!-- Add the Ohloh.com ID for the tool, if known. --><br />
{{Infobox_tool_details<br />
|ohloh_id=db-preservation-toolkit<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=Db-preservation-toolkit&diff=3264Db-preservation-toolkit2018-08-16T09:18:30Z<p>Lfaria: </p>
<hr />
<div><!-- Use the structure provided in this template, do not change it! --><br />
<br />
{{Infobox_tool<br />
|name=db-preservation-toolkit<br />
|purpose=Enables conversion between database formats or dumping from live database systems for the purposes of preservation.<br />
<!-- |image=image.png --><br />
|homepage=https://www.database-preservation.com<br />
|license=LGPL v3<br />
|platforms=Platform independent - Java<br />
}}<br />
<br />
<br />
<!-- Add one ore more categories to describe the function of the tool. Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). The following are common category examples, remove those that don't apply --><br />
[[Category:File Format Migration]]<br />
<br />
<br />
<!-- Add relevant categories to describe the content type that the tool addresses. Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. The following are common category examples, remove those that don't apply --><br />
[[Category:Database]]<br />
<br />
== Description == <br />
The Database Preservation Toolkit allows conversion between Database formats, including connection to live systems, for purposes of digitally preserving databases. The toolkit allows conversion of live or backed-up databases into preservation formats such as SIARD, a XML-based format created for the purpose of database preservation. The toolkit also allows conversion of the preservation formats back into live systems to allow the full functionality of databases.<br />
<br />
The Database Preservation Toolkit supports the following Database Management Systems:<br />
* MySQL/MariaDB<br />
* PostgreSQL<br />
* Oracle<br />
* Microsoft SQL Server<br />
* Microsoft Access<br />
* And other databases (using JDBC)<br />
<br />
Database Preservation Toolkit can convert any of the above DBMS to the following preservation formats:<br />
* SIARD 1<br />
* SIARD 2<br />
* SIARD DK<br />
<br />
The Database Preservation Toolkit is also capable of loading preserved databases into any of the above DBMS.<br />
<br />
== User Experiences ==<br />
<!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. --><br />
<br />
<br />
== Development Activity ==<br />
Code is being actively developed at [https://github.com/keeps/db-preservation-toolkit Database Preservation Toolkit GitHub repository].<br />
<br />
<br />
=== Release Feed ===<br />
Below the last 3 release feeds:<br />
<rss max=3>https://github.com/keeps/db-preservation-toolkit/releases.atom</rss><br />
<br />
<br />
=== Activity Feed===<br />
Below the last 5 commits:<br />
<rss max=5>https://github.com/keeps/db-preservation-toolkit/commits/master.atom</rss><br />
<br />
<br />
<!-- Add the Ohloh.com ID for the tool, if known. --><br />
{{Infobox_tool_details<br />
|ohloh_id=db-preservation-toolkit<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=Category:Digital_Repository&diff=1676Category:Digital Repository2014-01-24T17:06:48Z<p>Lfaria: </p>
<hr />
<div>[[Category:Function]]<br />
A system that allows storage and management of content and includes features to allow external users to find and access the content.</div>Lfariahttps://coptr.digipres.org/index.php?title=Roda&diff=1675Roda2014-01-24T15:19:40Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|name=RODA<br />
|purpose=RODA - Repository of Authentic Digital Objects<br />
|image=RODA-logo-basic.png<br />
|caption=RODA<br />
|alt=RODA<br />
|homepage=http://www.roda-community.org<br />
|license=LGPL v3<br />
|platforms=Server runs on Linux. Client runs on any web browser.<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Preservation System]][[Category:Digital Repository]]<br />
<br />
RODA is a digital repository created in conjunction with the Portuguese National Archives. Its primary objective is to allow long-term preservation and authenticity of digital objects of national importance. Based as much as possible on standards, following international specifications to become a trustworthy repository, as the OAIS/TRAC, and having high standards of security and scalability. The user interface was also an important consideration, as it was designed for archivists, producers, and consumers.<br />
<br />
= Features =<br />
<br />
RODA is a complete digital repository that delivers functionality for all the main units of the OAIS reference model. RODA is capable of ingesting, managing and providing access to the various types of digital content produced by large corporations or public bodies. RODA is based on open-source technologies and is supported by existing standards such as the OAIS, METS, EAD and PREMIS. <br />
<br />
* '''Conforms to open standards''' - RODA follows open standards using EAD for description metadata, PREMIS for preservation metadata, METS for structural metadata, and several standards for technical metadata (e.g. NISO Z39.87 for digital still images).<br />
* '''Vendor independent''' - RODA is 100% built on top of open-source technologies. The entire infrastructure required to support RODA is vendor independent. This means that you may use the hardware and Linux distributions that best fit your institutional needs.<br />
* '''Scalable''' - The service-oriented nature of RODA's architecture allows the system to be highly scalable, enabling the distribution of the processing load between several servers. Furthermore, new developments are in the works to enable RODA's preservation actions to be run over Hadoop clusters for even greater performance.<br />
* '''Embedded preservation actions''' - Preservation actions and management within RODA is handled by a task scheduler. The task scheduler allows the administrator to define the set of rules that trigger specific actions, and when these should take place. Preservation actions include format conversions, checksum verifications, reporting (e.g. to automatically send SIP acceptance/rejection emails), notification events, etc.<br />
* '''Authenticity''' - RODA uses preservation metadata (PREMIS) to create a trust chain between all format migrations and content verifications. The preservation metadata, together with the establishment of trust of its surrounding environment (ISO 16363) ensures reliability of the service and authenticity of the enclosed digital records.<br />
* '''Support for multiple formats''' - RODA is capable of ingesting and normalizing (according to the preservation plan in place) text documents, raster images, relational databases, video, and audio. A plug-in mechanism enables RODA to easily support additional formats.<br />
* '''Copes with the rapid changing nature of technology''' - The plug-in and task scheduling mechanism allows an easy way to add more functionality to the system (e.g. new preservation events, alerts, tools, etc.). Also, the service oriented architecture allows RODA base components to be incrementally updated, allowing a heterogeneous use of technologies at all levels: hardware, OS and applications.<br />
* '''Advanced access control''' - Users must be authenticated before accessing the repository. All user actions are logged for future accountability. Permissions are granular and can be defined at repository level, all the way down to individual data objects.<br />
* '''Integration with 3rd party systems''' - RODA exposes all its functionality via Web Services. Convenient Java libraries are available to allow developers to interact with RODA via its Core APIs. Several tools exist to create and manipulate the SIPs and submit them to RODA's ingest workflow.<br />
* '''Advanced ingest workflow''' - RODA supports the ingest of new digital material as well as associated metadata in 4 distinct ways: 1) online submission (self-archiving), 2) off-line submission using an client application called “RODA-in” (off-line self-archiving), 3) batch import by depositing SIPs via FTP or SMB/CIFS; and 4) integration with third-party document management software via invocation of SOAP Services or client API.<br />
<br />
= Development Activity =<br />
<br />
Code is being actively developed at [[https://github.com/keeps/roda RODA GitHub repository]]. Lastest version is RODA 1.2.0 (release at 2013-10-25) where the following new features were added:<br />
* Using Droid for file format identification<br />
* Added support for presentations: Microsoft Powerpoint (ppt, pptx), OpenOffice Presentation / LibreOffice Impress (odp)<br />
* Added support for spreadsheets: Microsoft Excel (xls, xlsx), OpenOffice Spreadsheet / LibreOffice Calc (ods)<br />
* Added support for email (.eml) but conversion is not yet supported<br />
* Added web service to download AIP<br />
* Added web service to download DIP<br />
<br />
<br />
For more information checkout the complete [[https://github.com/keeps/roda/blob/master/CHANGELOG.txt change log]].<br />
<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=Roda<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=Roda&diff=1674Roda2014-01-24T15:19:06Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|name=RODA<br />
|purpose=RODA - Repository of Authentic Digital Objects<br />
|image=RODA-logo-basic.png<br />
|caption=RODA<br />
|alt=RODA<br />
|homepage=http://www.roda-community.org<br />
|license=LGPL v3<br />
|platforms=Server runs on Linux. Client runs on any web browser.<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Preservation System]][[Category:Digital Repository]]<br />
<br />
RODA is a digital repository created in conjunction with the Portuguese National Archives. Its primary objective is to allow long-term preservation and authenticity of digital objects of national importance. Based as much as possible on standards, following international specifications to become a trustworthy repository, as the OAIS/TRAC, and having high standards of security and scalability. The user interface was also an important consideration, as it was designed for archivists, producers, and consumers.<br />
<br />
= Features =<br />
<br />
RODA is a complete digital repository that delivers functionality for all the main units of the OAIS reference model. RODA is capable of ingesting, managing and providing access to the various types of digital content produced by large corporations or public bodies. RODA is based on open-source technologies and is supported by existing standards such as the OAIS, METS, EAD and PREMIS. <br />
<br />
* '''Conforms to open standards''' - RODA follows open standards using EAD for description metadata, PREMIS for preservation metadata, METS for structural metadata, and several standards for technical metadata (e.g. NISO Z39.87 for digital still images).<br />
* '''Vendor independent''' - RODA is 100% built on top of open-source technologies. The entire infrastructure required to support RODA is vendor independent. This means that you may use the hardware and Linux distributions that best fit your institutional needs.<br />
* '''Scalable''' - The service-oriented nature of RODA's architecture allows the system to be highly scalable, enabling the distribution of the processing load between several servers. Furthermore, new developments are in the works to enable RODA's preservation actions to be run over Hadoop clusters for even greater performance.<br />
* '''Embedded preservation actions''' - Preservation actions and management within RODA is handled by a task scheduler. The task scheduler allows the administrator to define the set of rules that trigger specific actions, and when these should take place. Preservation actions include format conversions, checksum verifications, reporting (e.g. to automatically send SIP acceptance/rejection emails), notification events, etc.<br />
* '''Authenticity''' - RODA uses preservation metadata (PREMIS) to create a trust chain between all format migrations and content verifications. The preservation metadata, together with the establishment of trust of its surrounding environment (ISO 16363) ensures reliability of the service and authenticity of the enclosed digital records.<br />
* '''Support for multiple formats''' - RODA is capable of ingesting and normalizing (according to the preservation plan in place) text documents, raster images, relational databases, video, and audio. A plug-in mechanism enables RODA to easily support additional formats.<br />
* '''Copes with the rapid changing nature of technology''' - The plug-in and task scheduling mechanism allows an easy way to add more functionality to the system (e.g. new preservation events, alerts, tools, etc.). Also, the service oriented architecture allows RODA base components to be incrementally updated, allowing a heterogeneous use of technologies at all levels: hardware, OS and applications.<br />
* '''Advanced access control''' - Users must be authenticated before accessing the repository. All user actions are logged for future accountability. Permissions are granular and can be defined at repository level, all the way down to individual data objects.<br />
* '''Integration with 3rd party systems''' - RODA exposes all its functionality via Web Services. Convenient Java libraries are available to allow developers to interact with RODA via its Core APIs. Several tools exist to create and manipulate the SIPs and submit them to RODA's ingest workflow.<br />
* '''Advanced ingest workflow''' - RODA supports the ingest of new digital material as well as associated metadata in 4 distinct ways: 1) online submission (self-archiving), 2) off-line submission using an client application called “RODA-in” (off-line self-archiving), 3) batch import by depositing SIPs via FTP or SMB/CIFS; and 4) integration with third-party document management software via invocation of SOAP Services or client API.<br />
<br />
= Development Activity =<br />
<br />
Code is being actively developed at [[https://github.com/keeps/roda RODA GitHub repository]]. Lastest version is RODA 1.2.0 (release at 2013-10-25) where the following new features were added:<br />
* Using Droid for file format identification<br />
* Added support for presentations: Microsoft Powerpoint (ppt, pptx), OpenOffice Presentation / LibreOffice Impress (odp)<br />
* Added support for spreadsheets: Microsoft Excel (xls, xlsx), OpenOffice Spreadsheet / LibreOffice Calc (ods)<br />
* Added support for email (.eml) but conversion is not yet supported<br />
* Added web service to download AIP<br />
* Added web service to download DIP<br />
<br />
<br />
For more information checkout the complete [[https://github.com/keeps/roda/blob/master/CHANGELOG.txt change log]].<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=Roda<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=Fedora_Commons&diff=1673Fedora Commons2014-01-24T14:51:41Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|purpose=Fedora provides the back-end foundation for digital repository systems responsible for managing and preserving all types of digital content.<br />
|image=<br />
|homepage=http://fedora-commons.org/<br />
|license=<br />
|platforms=<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Digital Repository]]<br />
<br />
<br />
= Description =<br />
[http://fedora-commons.org/ Fedora] provides the back-end foundation for digital repository systems responsible for managing and preserving all types of digital content.<br />
====Provider====<br />
DuraSpace/Fedora Commons<br />
====Licensing and cost====<br />
[http://www.apache.org/licenses/LICENSE-2.0.html Apache 2.0] &ndash; free.<br />
====Development Activity====<br />
Version 3.6.2 was released 15 November 2012.<br />
Development is ongoing. The [https://wiki.duraspace.org/display/FF/Fedora+Futures+Home Fedora Futures] initiative was created in December 2012 to take a long-term view of Fedora development. This initiative is developing Fedora 4.0, re-architecting the software to accommodate recent software and technology advances as appropriate.<br />
====Platform and interoperability====<br />
Fedora is written in Java, and was tested under Linux, Solaris, Windows, and Mac OS X.<br />
====Functional Notes====<br />
In the Fedora digital object model, an object consists of a persistent identifier, an XML document for object properties, and a number of datastreams each holding a content file or metadata record (the object can have more than one of each). Each object can assert relationships to any number of other objects using RDF. The XML object properties documents contain information such as an audit trail of actions that have affected the object and policies about the object; as long as these files, along with the content itself, are backed up properly, they can be used to reconstruct an entire running instance of the repository without relying on any external software.<br />
While the Fedora Repository is capable of operating as a standalone content server, it is designed for use with other software to provide full system functionality. Such software might include authoring or ingest applications, search engines, workflow management, or security components such as user identity management.<br />
====Documentation and user support====<br />
The Fedora Commons community is extensive, with active [http://www.fedora-commons.org/community/userlist user] and [http://www.fedora-commons.org/community/developers/devlist developer] mailing lists; DuraSpace also hosts a Fedora [https://wiki.duraspace.org/display/FEDORA/Home wiki], which includes tutorials, user and installation guides, and other resources.<br />
The Fedora site also links to a number of [http://www.fedora-commons.org/resources/serviceproviders registered service providers], which offer assistance with design, installation, and implementation.<br />
====Usability====<br />
Fedora provides a web-based Administrator GUI for low-level object editing; users, however, interact with the repository using APIs for management, access, search, and queries. Usability more broadly is dependent on the interfaces that the system administrator has chosen as front ends for the APIs: this model was chosen so that different interfaces can be designed to suit different needs. The Fedora wiki includes a registry of community-developed software that provides these kinds of interfaces; frameworks to facilitate such development include [http://projecthydra.org Hydra] and [http://islandora.ca Islandora].<br />
====Expertise required====<br />
Installation and configuration require detailed system administration knowledge, as well as expertise in XML and interface design. The Hydra and Islandora frameworks seek to alleviate this by 'hiding' Fedora behind simpler system environments based on Ruby on Rails and Drupal, respectively.<br />
====Standards compliance====<br />
Fedora supports OAI-PMH (and by extension, Dublin Core and other metadata standards), and also provides support for RDF.<br />
====Influence and take-up====<br />
The [https://wiki.duraspace.org/display/FCCommReg/Fedora+Commons+Registry Fedora Commons Registry] lists nearly 200 organisations with Fedora instances, from broadcast services such as WGBH, to government agencies such as the U.S. Centers for Disease Control and Prevention, to academic archives such as Oxford University.<br />
<br />
<br />
= User Experiences =<br />
<br />
<br />
= Development Activity =<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=Fedora Commons<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=DuraCloud&diff=1672DuraCloud2014-01-24T14:51:36Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|purpose=DuraCloud is a hosted service that provides a centralised interface for organizations interested in using cloud storage as a part of their digital archiving and preservation programs.<br />
|image=<br />
|homepage=http://www.duracloud.org/<br />
|license=Apache License<br />
|platforms=Web based<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Service]]<br />
<br />
<br />
= Description =<br />
[http://www.duracloud.org/ DuraCloud] is a hosted service that provides a centralised interface for organizations interested in using cloud storage as a part of their digital archiving and preservation programs.&nbsp;DuraCloud negotiates with commercial cloud storage providers such as Amazon Web Services and Windows Azure, coordinating content within these existing infrastructures. &nbsp;It allows users to have multiple copies of their content on multiple clouds, without increasing procedural complications.<br />
====Provider====<br />
The DuraSpace organization<br />
====Licensing and cost====<br />
[http://www.apache.org/licenses/LICENSE-2.0.html Apache License, Version 2.0]. &nbsp;Service fees from $4,500-$7,000 per year.&nbsp;<br />
====Development activity====<br />
DuraCloud 2.3.1 was released in Spring 2013.<br />
DuraSpace is a self-funded not-for-profit organisation; DuraCloud is one of their core services, receiving ongoing development and support. &nbsp;The organisation has been developing a storage service aimed directly towards researchers.<br />
====Platform and interoperability====<br />
As a web interface, DuraCloud is platform agnostic.<br />
DuraCloud offers an API to allow users to integrate it directly into their systems.<br />
If building from sourcecode, the DuraCloud software currently supports integration with Amazon S3, Windows Azure, Rackspace CloudFiles, and SDSC cloud. The system must have Maven 2.2.1 or above, Tomcat 6.x or above, Java 6, and Subversion installed.<br />
====Functional notes====<br />
As a storage and archiving platform, DuraCloud allows users to duplicate content over multiple clouds, to transform images from one format to another, and to check bit integrity. &nbsp;As an access platform, DuraCloud offers an image server and a media streamer. &nbsp;<br />
====Documentation and user support====<br />
User support is included in the subscription fee. &nbsp;Extensive information is available through a public [https://wiki.duraspace.org/display/DURACLOUD/DuraCloud wiki], including formal documentation. &nbsp;DuraCloud also hosts a public issue-tracker.<br />
====Usability====<br />
The service provides a straightforward web interface for administrative functions. &nbsp;<br />
====Expertise required====<br />
Basic functions do not require special expertise, although integration into organisational workflows or user access platforms requires significant systems experience.<br />
====Standards compliance====<br />
DuraCloud conforms to REST architecture standards.<br />
====Influence and take-up====<br />
DuraCloud is used by organisations such as the U.S. public television station WGBH, the Interuniversity Consortium for Political and Social Research, and MIT.<br />
<br />
= User Experiences =<br />
<br />
<br />
= Development Activity =<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=DuraCloud<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=DSpace&diff=1671DSpace2014-01-24T14:49:45Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|purpose=DSpace is an institutional repository system which enables easy deposit, preservation, and access for all types of digital content.<br />
|image=<br />
|homepage=http://www.dspace.org/<br />
|license=BSD<br />
|platforms=<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Digital Repository]]<br />
<br />
<br />
= Description =<br />
[http://www.dspace.org/ DSpace] is an institutional repository system which enables easy deposit, preservation, and access for all types of digital content.&nbsp;<br />
====Provider====<br />
DuraSpace<br />
====Licensing and cost====<br />
[http://www.linfo.org/bsdlicense.html BSD Open Source License] - free<br />
====Development Activity====<br />
DSpace 1.8.1 was released in December 2011.<br />
Development is ongoing. In late 2011 the DSpace Community Advisory Team decided to forgo releasing a version 2.0; instead, version 3.0 will be released in Fall 2012.<br />
====Platform and interoperability====<br />
DSpace is written in Java, providing a web based interface that can be installed in Linux, Mac OSX or Windows environments. It requires either a PostgreSQL or Oracle database. The software comes with plugins for most university authentication methods, including: LDAP (and hierarchical LDAP), Shibboleth, X.509, and IP-based.<br />
====Functional Notes====<br />
The DSpace data model is intended to reflect the structure of the organization using the system. Each DSpace site is divided into communities, which can be further divided into sub-communities reflecting the typical university structure of college, department, research centre, or laboratory. Communities contain collections, which are groupings of related content. Each collection is composed of items, which are the basic archival elements of the archive. Items are further subdivided into named bundles of bitstreams.<br />
Workflows are unidirectional &ndash; e.g. an item can&rsquo;t move from Live to Pending.<br />
DSpace administrators can create multiple user roles, which allows for extremely fine-tuned access rights.<br />
====Documentation and user support====<br />
DSpace offers a wealth of documentation and user support. The website includes an extensive [https://wiki.duraspace.org/display/DSDOC/All+Documentation Documentation Wiki], and supports a number of mailing lists. Users can report and track errors through a JIRA system. The site also links to tutorials, how-to&rsquo;s, and other training materials.<br />
As of 2011, there are seven registered service providers and 22 non-registered providers, offering presumably fee-based support . DSpace also has an Ambassador Program, which attempts to identify a DSpace user in every country or region who is willing to volunteer to be a point of contact for organizations just getting started.<br />
====Usability====<br />
DSpace does not include an installation and configuration tool, or &lsquo;wizard,&rsquo; which makes these processes time consuming and challenging for users without system administration training.<br />
A number of organisations using DSpace have performed usability analyses of their repositories. While the overall structure works well, many organisations found that naming conventions were sometimes confusing for users. In addition, many users expected that the search mechanism would automatically include a Boolean AND, which is not the case.<br />
====Expertise required====<br />
Installation and configuration greatly benefit from system administration knowledge, as well as a deep understanding of repository structures and workflows.<br />
====Standards compliance====<br />
DSpace supports OAI-PMH, OAI-ORE, SWORD, SWORD2, WebDAV, OpenSearch, OpenURL, RSS, and ATOM.<br />
DSpace metadata uses the Dublin Core standard.<br />
====Influence and take-up====<br />
As of 2011, over 1100 organizations currently use the DSpace software in a production or project environment. A full list of known DSpace instances can be found at [http://www.dspace.org/whos-using-dspace http://www.dspace.org/whos-using-dspace].<br />
<br />
<br />
= User Experiences =<br />
<br />
<br />
= Development Activity =<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=DSpace<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=EPrints&diff=1670EPrints2014-01-24T14:48:48Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|purpose=EPrints is an open access digital repository software, which is intended to create a highly configurable web-based repository.<br />
|image=<br />
|homepage=http://www.eprints.org/<br />
|license=GPLv3 and LGPLv3<br />
|platforms=<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Digital Repository]]<br />
<br />
<br />
= Description =<br />
[http://www.eprints.org/ EPrints] is an open access digital repository software, which is intended to create a highly configurable web-based repository.<br />
The EPrints organisation also provides a number of services, including hosting, customization, importing legacy data, providing training and support, advising on policy development, assisting with advocacy and promotion, and providing project management.<br />
====Provider====<br />
University of Southampton<br />
====Licensing and cost====<br />
[http://www.gnu.org/licenses/gpl.html Gnu Public License (GPL)] - free<br />
====Development Activity====<br />
EPrints 3.3.7 was released in December 2011.<br />
Development is ongoing as of writing.&nbsp;<br />
====Platform and interoperability====<br />
EPrints is written in Perl.&nbsp; It was developed on Redhat Linux, but it can be used on UNIX-like systems including OS-X. It also runs on Windows Vista and XP.<br />
EPrints is able to export data into BibTeX, refer, EndNote &amp; other bibliography managers, as well as Google Earth, Similie TimeLine or other Web Services.<br />
====Functional Notes====<br />
The EPrints data model consists of three core objects: the EPrint, the Document, and the User.&nbsp; Users have stated that this allows the creation of more complex hierarchies than with other repository software.<br />
EPrints does not automatically support Handle.<br />
====Documentation and user support====<br />
EPrints Services offers fee-based support for repositories. The EP-Tech mailing list offers free support and discussion about EPrints; however, it is unclear how active this mailing list is. The site also links to a bug-tracker.<br />
The EPrints website offers extensive documentation via a [http://wiki.eprints.org/w/Main_Page wiki], including an installation manual, user guide, and training materials. While much of the information is up-to-date and clearly organised, a recent migration (as of November 2011) has left a number of the pages with error messages, or notices that the material &ldquo;needs sorting out&rdquo;.<br />
====Usability====<br />
An installation script automates most of the installation processes.<br />
Development for version 3 included an extensive usability analysis, which resulted in substantial redesign of the metadata entry process. A key component is the new auto-complete function.<br />
====Expertise required====<br />
Installation and configuration greatly benefit from system administration knowledge, as well as a deep understanding of repository structures and workflows.<br />
====Standards compliance====<br />
EPrints is OAI compliant. It provides support for METS, Dublin Core and other DL interoperability formats.<br />
====Influence and take-up====<br />
EPrints is widely used in European archives and repositories. Organisations using EPrints include University College London Research, the Glasgow Theses Services, and the Queensland Department of Employment, Economic Development and Innovation.<br />
<br />
<br />
= User Experiences =<br />
<br />
<br />
= Development Activity =<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=EPrints<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=EPrints&diff=1669EPrints2014-01-24T14:47:42Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|purpose=EPrints is an open access digital repository software, which is intended to create a highly configurable web-based repository.<br />
|image=<br />
|homepage=http://www.eprints.org/<br />
|license=<br />
|platforms=<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Digital Repository]]<br />
<br />
<br />
= Description =<br />
[http://www.eprints.org/ EPrints] is an open access digital repository software, which is intended to create a highly configurable web-based repository.<br />
The EPrints organisation also provides a number of services, including hosting, customization, importing legacy data, providing training and support, advising on policy development, assisting with advocacy and promotion, and providing project management.<br />
====Provider====<br />
University of Southampton<br />
====Licensing and cost====<br />
[http://www.gnu.org/licenses/gpl.html Gnu Public License (GPL)] - free<br />
====Development Activity====<br />
EPrints 3.3.7 was released in December 2011.<br />
Development is ongoing as of writing.&nbsp;<br />
====Platform and interoperability====<br />
EPrints is written in Perl.&nbsp; It was developed on Redhat Linux, but it can be used on UNIX-like systems including OS-X. It also runs on Windows Vista and XP.<br />
EPrints is able to export data into BibTeX, refer, EndNote &amp; other bibliography managers, as well as Google Earth, Similie TimeLine or other Web Services.<br />
====Functional Notes====<br />
The EPrints data model consists of three core objects: the EPrint, the Document, and the User.&nbsp; Users have stated that this allows the creation of more complex hierarchies than with other repository software.<br />
EPrints does not automatically support Handle.<br />
====Documentation and user support====<br />
EPrints Services offers fee-based support for repositories. The EP-Tech mailing list offers free support and discussion about EPrints; however, it is unclear how active this mailing list is. The site also links to a bug-tracker.<br />
The EPrints website offers extensive documentation via a [http://wiki.eprints.org/w/Main_Page wiki], including an installation manual, user guide, and training materials. While much of the information is up-to-date and clearly organised, a recent migration (as of November 2011) has left a number of the pages with error messages, or notices that the material &ldquo;needs sorting out&rdquo;.<br />
====Usability====<br />
An installation script automates most of the installation processes.<br />
Development for version 3 included an extensive usability analysis, which resulted in substantial redesign of the metadata entry process. A key component is the new auto-complete function.<br />
====Expertise required====<br />
Installation and configuration greatly benefit from system administration knowledge, as well as a deep understanding of repository structures and workflows.<br />
====Standards compliance====<br />
EPrints is OAI compliant. It provides support for METS, Dublin Core and other DL interoperability formats.<br />
====Influence and take-up====<br />
EPrints is widely used in European archives and repositories. Organisations using EPrints include University College London Research, the Glasgow Theses Services, and the Queensland Department of Employment, Economic Development and Innovation.<br />
<br />
<br />
= User Experiences =<br />
<br />
<br />
= Development Activity =<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=EPrints<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=DSpace&diff=1668DSpace2014-01-24T14:46:53Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|purpose=DSpace is an institutional repository system which enables easy deposit, preservation, and access for all types of digital content.<br />
|image=<br />
|homepage=http://www.dspace.org/<br />
|license=<br />
|platforms=<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Digital Repository]]<br />
<br />
<br />
= Description =<br />
[http://www.dspace.org/ DSpace] is an institutional repository system which enables easy deposit, preservation, and access for all types of digital content.&nbsp;<br />
====Provider====<br />
DuraSpace<br />
====Licensing and cost====<br />
[http://www.linfo.org/bsdlicense.html BSD Open Source License] - free<br />
====Development Activity====<br />
DSpace 1.8.1 was released in December 2011.<br />
Development is ongoing. In late 2011 the DSpace Community Advisory Team decided to forgo releasing a version 2.0; instead, version 3.0 will be released in Fall 2012.<br />
====Platform and interoperability====<br />
DSpace is written in Java, providing a web based interface that can be installed in Linux, Mac OSX or Windows environments. It requires either a PostgreSQL or Oracle database. The software comes with plugins for most university authentication methods, including: LDAP (and hierarchical LDAP), Shibboleth, X.509, and IP-based.<br />
====Functional Notes====<br />
The DSpace data model is intended to reflect the structure of the organization using the system. Each DSpace site is divided into communities, which can be further divided into sub-communities reflecting the typical university structure of college, department, research centre, or laboratory. Communities contain collections, which are groupings of related content. Each collection is composed of items, which are the basic archival elements of the archive. Items are further subdivided into named bundles of bitstreams.<br />
Workflows are unidirectional &ndash; e.g. an item can&rsquo;t move from Live to Pending.<br />
DSpace administrators can create multiple user roles, which allows for extremely fine-tuned access rights.<br />
====Documentation and user support====<br />
DSpace offers a wealth of documentation and user support. The website includes an extensive [https://wiki.duraspace.org/display/DSDOC/All+Documentation Documentation Wiki], and supports a number of mailing lists. Users can report and track errors through a JIRA system. The site also links to tutorials, how-to&rsquo;s, and other training materials.<br />
As of 2011, there are seven registered service providers and 22 non-registered providers, offering presumably fee-based support . DSpace also has an Ambassador Program, which attempts to identify a DSpace user in every country or region who is willing to volunteer to be a point of contact for organizations just getting started.<br />
====Usability====<br />
DSpace does not include an installation and configuration tool, or &lsquo;wizard,&rsquo; which makes these processes time consuming and challenging for users without system administration training.<br />
A number of organisations using DSpace have performed usability analyses of their repositories. While the overall structure works well, many organisations found that naming conventions were sometimes confusing for users. In addition, many users expected that the search mechanism would automatically include a Boolean AND, which is not the case.<br />
====Expertise required====<br />
Installation and configuration greatly benefit from system administration knowledge, as well as a deep understanding of repository structures and workflows.<br />
====Standards compliance====<br />
DSpace supports OAI-PMH, OAI-ORE, SWORD, SWORD2, WebDAV, OpenSearch, OpenURL, RSS, and ATOM.<br />
DSpace metadata uses the Dublin Core standard.<br />
====Influence and take-up====<br />
As of 2011, over 1100 organizations currently use the DSpace software in a production or project environment. A full list of known DSpace instances can be found at [http://www.dspace.org/whos-using-dspace http://www.dspace.org/whos-using-dspace].<br />
<br />
<br />
= User Experiences =<br />
<br />
<br />
= Development Activity =<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=DSpace<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=Category:Digital_Repository&diff=1667Category:Digital Repository2014-01-24T14:45:40Z<p>Lfaria: Created page with "A system that allows storage and management of content and includes features to allow external users to find and access the content."</p>
<hr />
<div>A system that allows storage and management of content and includes features to allow external users to find and access the content.</div>Lfariahttps://coptr.digipres.org/index.php?title=Roda&diff=1666Roda2014-01-24T14:39:44Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|name=RODA<br />
|purpose=RODA - Repository of Authentic Digital Objects<br />
|image=RODA-logo-basic.png<br />
|caption=RODA<br />
|alt=RODA<br />
|homepage=http://www.roda-community.org<br />
|license=LGPL v3<br />
|platforms=Server runs on Linux. Client runs on any web browser.<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Preservation System]][[Category:Digital Repository]]<br />
<br />
<br />
= Description =<br />
<br />
RODA is a digital repository created in conjunction with the Portuguese National Archives. Its primary objective is to allow long-term preservation and authenticity of digital objects of national importance. Based as much as possible on standards, following international specifications to become a trustworthy repository, as the OAIS/TRAC, and having high standards of security and scalability. The user interface was also an important consideration, as it was designed for archivists, producers, and consumers.<br />
<br />
= Features =<br />
<br />
RODA is a complete digital repository that delivers functionality for all the main units of the OAIS reference model. RODA is capable of ingesting, managing and providing access to the various types of digital content produced by large corporations or public bodies. RODA is based on open-source technologies and is supported by existing standards such as the OAIS, METS, EAD and PREMIS. <br />
<br />
* '''Conforms to open standards''' - RODA follows open standards using EAD for description metadata, PREMIS for preservation metadata, METS for structural metadata, and several standards for technical metadata (e.g. NISO Z39.87 for digital still images).<br />
* '''Vendor independent''' - RODA is 100% built on top of open-source technologies. The entire infrastructure required to support RODA is vendor independent. This means that you may use the hardware and Linux distributions that best fit your institutional needs.<br />
* '''Scalable''' - The service-oriented nature of RODA's architecture allows the system to be highly scalable, enabling the distribution of the processing load between several servers. Furthermore, new developments are in the works to enable RODA's preservation actions to be run over Hadoop clusters for even greater performance.<br />
* '''Embedded preservation actions''' - Preservation actions and management within RODA is handled by a task scheduler. The task scheduler allows the administrator to define the set of rules that trigger specific actions, and when these should take place. Preservation actions include format conversions, checksum verifications, reporting (e.g. to automatically send SIP acceptance/rejection emails), notification events, etc.<br />
* '''Authenticity''' - RODA uses preservation metadata (PREMIS) to create a trust chain between all format migrations and content verifications. The preservation metadata, together with the establishment of trust of its surrounding environment (ISO 16363) ensures reliability of the service and authenticity of the enclosed digital records.<br />
* '''Support for multiple formats''' - RODA is capable of ingesting and normalizing (according to the preservation plan in place) text documents, raster images, relational databases, video, and audio. A plug-in mechanism enables RODA to easily support additional formats.<br />
* '''Copes with the rapid changing nature of technology''' - The plug-in and task scheduling mechanism allows an easy way to add more functionality to the system (e.g. new preservation events, alerts, tools, etc.). Also, the service oriented architecture allows RODA base components to be incrementally updated, allowing a heterogeneous use of technologies at all levels: hardware, OS and applications.<br />
* '''Advanced access control''' - Users must be authenticated before accessing the repository. All user actions are logged for future accountability. Permissions are granular and can be defined at repository level, all the way down to individual data objects.<br />
* '''Integration with 3rd party systems''' - RODA exposes all its functionality via Web Services. Convenient Java libraries are available to allow developers to interact with RODA via its Core APIs. Several tools exist to create and manipulate the SIPs and submit them to RODA's ingest workflow.<br />
* '''Advanced ingest workflow''' - RODA supports the ingest of new digital material as well as associated metadata in 4 distinct ways: 1) online submission (self-archiving), 2) off-line submission using an client application called “RODA-in” (off-line self-archiving), 3) batch import by depositing SIPs via FTP or SMB/CIFS; and 4) integration with third-party document management software via invocation of SOAP Services or client API.<br />
<br />
<br />
<br />
<br />
= Development Activity =<br />
<br />
Code is being actively developed at [[https://github.com/keeps/roda RODA GitHub repository]]. Lastest version is RODA 1.2.0 (release at 2013-10-25) where the following new features were added:<br />
* Using Droid for file format identification<br />
* Added support for presentations: Microsoft Powerpoint (ppt, pptx), OpenOffice Presentation / LibreOffice Impress (odp)<br />
* Added support for spreadsheets: Microsoft Excel (xls, xlsx), OpenOffice Spreadsheet / LibreOffice Calc (ods)<br />
* Added support for email (.eml) but conversion is not yet supported<br />
* Added web service to download AIP<br />
* Added web service to download DIP<br />
<br />
<br />
For more information checkout the complete [[https://github.com/keeps/roda/blob/master/CHANGELOG.txt change log]].<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=Roda<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=Roda&diff=1665Roda2014-01-24T12:25:11Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|name=RODA<br />
|purpose=RODA - Repository of Authentic Digital Objects<br />
|image=RODA-logo-basic.png<br />
|caption=RODA<br />
|alt=RODA<br />
|homepage=http://www.roda-community.org<br />
|license=LGPL v3<br />
|platforms=Server runs on Linux. Client runs on any web browser.<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Preservation System]]<br />
<br />
<br />
= Description =<br />
<br />
RODA is a digital repository created in conjunction with the Portuguese National Archives. Its primary objective is to allow long-term preservation and authenticity of digital objects of national importance. Based as much as possible on standards, following international specifications to become a trustworthy repository, as the OAIS/TRAC, and having high standards of security and scalability. The user interface was also an important consideration, as it was designed for archivists, producers, and consumers.<br />
<br />
= Features =<br />
<br />
RODA is a complete digital repository that delivers functionality for all the main units of the OAIS reference model. RODA is capable of ingesting, managing and providing access to the various types of digital content produced by large corporations or public bodies. RODA is based on open-source technologies and is supported by existing standards such as the OAIS, METS, EAD and PREMIS. <br />
<br />
* '''Conforms to open standards''' - RODA follows open standards using EAD for description metadata, PREMIS for preservation metadata, METS for structural metadata, and several standards for technical metadata (e.g. NISO Z39.87 for digital still images).<br />
* '''Vendor independent''' - RODA is 100% built on top of open-source technologies. The entire infrastructure required to support RODA is vendor independent. This means that you may use the hardware and Linux distributions that best fit your institutional needs.<br />
* '''Scalable''' - The service-oriented nature of RODA's architecture allows the system to be highly scalable, enabling the distribution of the processing load between several servers. Furthermore, new developments are in the works to enable RODA's preservation actions to be run over Hadoop clusters for even greater performance.<br />
* '''Embedded preservation actions''' - Preservation actions and management within RODA is handled by a task scheduler. The task scheduler allows the administrator to define the set of rules that trigger specific actions, and when these should take place. Preservation actions include format conversions, checksum verifications, reporting (e.g. to automatically send SIP acceptance/rejection emails), notification events, etc.<br />
* '''Authenticity''' - RODA uses preservation metadata (PREMIS) to create a trust chain between all format migrations and content verifications. The preservation metadata, together with the establishment of trust of its surrounding environment (ISO 16363) ensures reliability of the service and authenticity of the enclosed digital records.<br />
* '''Support for multiple formats''' - RODA is capable of ingesting and normalizing (according to the preservation plan in place) text documents, raster images, relational databases, video, and audio. A plug-in mechanism enables RODA to easily support additional formats.<br />
* '''Copes with the rapid changing nature of technology''' - The plug-in and task scheduling mechanism allows an easy way to add more functionality to the system (e.g. new preservation events, alerts, tools, etc.). Also, the service oriented architecture allows RODA base components to be incrementally updated, allowing a heterogeneous use of technologies at all levels: hardware, OS and applications.<br />
* '''Advanced access control''' - Users must be authenticated before accessing the repository. All user actions are logged for future accountability. Permissions are granular and can be defined at repository level, all the way down to individual data objects.<br />
* '''Integration with 3rd party systems''' - RODA exposes all its functionality via Web Services. Convenient Java libraries are available to allow developers to interact with RODA via its Core APIs. Several tools exist to create and manipulate the SIPs and submit them to RODA's ingest workflow.<br />
* '''Advanced ingest workflow''' - RODA supports the ingest of new digital material as well as associated metadata in 4 distinct ways: 1) online submission (self-archiving), 2) off-line submission using an client application called “RODA-in” (off-line self-archiving), 3) batch import by depositing SIPs via FTP or SMB/CIFS; and 4) integration with third-party document management software via invocation of SOAP Services or client API.<br />
<br />
<br />
<br />
<br />
= Development Activity =<br />
<br />
Code is being actively developed at [[https://github.com/keeps/roda RODA GitHub repository]]. Lastest version is RODA 1.2.0 (release at 2013-10-25) where the following new features were added:<br />
* Using Droid for file format identification<br />
* Added support for presentations: Microsoft Powerpoint (ppt, pptx), OpenOffice Presentation / LibreOffice Impress (odp)<br />
* Added support for spreadsheets: Microsoft Excel (xls, xlsx), OpenOffice Spreadsheet / LibreOffice Calc (ods)<br />
* Added support for email (.eml) but conversion is not yet supported<br />
* Added web service to download AIP<br />
* Added web service to download DIP<br />
<br />
<br />
For more information checkout the complete [[https://github.com/keeps/roda/blob/master/CHANGELOG.txt change log]].<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=Roda<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=Roda&diff=1664Roda2014-01-24T12:24:17Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|name=RODA<br />
|purpose=RODA - Repository of Authentic Digital Objects<br />
|image=RODA-logo-basic.png<br />
|caption=RODA<br />
|alt=RODA<br />
|homepage=http://www.roda-community.org<br />
|license=LGPL v3<br />
|platforms=Server runs on Linux. Client runs on any web browser.<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Preservation System]]<br />
<br />
<br />
= Description =<br />
<br />
RODA is a digital repository created in conjunction with the Portuguese National Archives. Its primary objective is to allow long-term preservation and authenticity of digital objects of national importance. Based as much as possible on standards, following international specifications to become a trustworthy repository, as the OAIS/TRAC, and having high standards of security and scalability. The user interface was also an important consideration, as it was designed for archivists, producers, and consumers.<br />
<br />
= Features =<br />
<br />
RODA is a complete digital repository that delivers functionality for all the main units of the OAIS reference model. RODA is capable of ingesting, managing and providing access to the various types of digital content produced by large corporations or public bodies. RODA is based on open-source technologies and is supported by existing standards such as the OAIS, METS, EAD and PREMIS. <br />
<br />
* '''Conforms to open standards''' - RODA follows open standards using EAD for description metadata, PREMIS for preservation metadata, METS for structural metadata, and several standards for technical metadata (e.g. NISO Z39.87 for digital still images).<br />
* '''Vendor independent''' - RODA is 100% built on top of open-source technologies. The entire infrastructure required to support RODA is vendor independent. This means that you may use the hardware and Linux distributions that best fit your institutional needs.<br />
* '''Scalable''' - The service-oriented nature of RODA's architecture allows the system to be highly scalable, enabling the distribution of the processing load between several servers. Furthermore, new developments are in the works to enable RODA's preservation actions to be run over Hadoop clusters for even greater performance.<br />
* '''Embedded preservation actions''' - Preservation actions and management within RODA is handled by a task scheduler. The task scheduler allows the administrator to define the set of rules that trigger specific actions, and when these should take place. Preservation actions include format conversions, checksum verifications, reporting (e.g. to automatically send SIP acceptance/rejection emails), notification events, etc.<br />
* '''Authenticity''' - RODA uses preservation metadata (PREMIS) to create a trust chain between all format migrations and content verifications. The preservation metadata, together with the establishment of trust of its surrounding environment (ISO 16363) ensures reliability of the service and authenticity of the enclosed digital records.<br />
* '''Support for multiple formats''' - RODA is capable of ingesting and normalizing (according to the preservation plan in place) text documents, raster images, relational databases, video, and audio. A plug-in mechanism enables RODA to easily support additional formats.<br />
* '''Copes with the rapid changing nature of technology''' - The plug-in and task scheduling mechanism allows an easy way to add more functionality to the system (e.g. new preservation events, alerts, tools, etc.). Also, the service oriented architecture allows RODA base components to be incrementally updated, allowing a heterogeneous use of technologies at all levels: hardware, OS and applications.<br />
* '''Advanced access control''' - Users must be authenticated before accessing the repository. All user actions are logged for future accountability. Permissions are granular and can be defined at repository level, all the way down to individual data objects.<br />
* '''Integration with 3rd party systems''' - RODA exposes all its functionality via Web Services. Convenient Java libraries are available to allow developers to interact with RODA via its Core APIs. Several tools exist to create and manipulate the SIPs and submit them to RODA's ingest workflow.<br />
* '''Advanced ingest workflow''' - RODA supports the ingest of new digital material as well as associated metadata in 4 distinct ways: 1) online submission (self-archiving), 2) off-line submission using an client application called “RODA-in” (off-line self-archiving), 3) batch import by depositing SIPs via FTP or SMB/CIFS; and 4) integration with third-party document management software via invocation of SOAP Services or client API.<br />
<br />
<br />
<br />
<br />
= Development Activity =<br />
<br />
Code is being actively developed at [[https://github.com/keeps/roda RODA GitHub repository]]. Last version is RODA 1.2.0 (release at 2013-10-25) where the following new features were added:<br />
* Using Droid for file format identification<br />
* Added support for presentations: Microsoft Powerpoint (ppt, pptx), OpenOffice Presentation / LibreOffice Impress (odp)<br />
* Added support for spreadsheets: Microsoft Excel (xls, xlsx), OpenOffice Spreadsheet / LibreOffice Calc (ods)<br />
* Added support for email (.eml) but conversion is not yet supported<br />
* Added web service to download AIP<br />
* Added web service to download DIP<br />
<br />
<br />
For more information checkout the complete [[https://github.com/keeps/roda/blob/master/CHANGELOG.txt change log]].<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=Roda<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=Roda&diff=1663Roda2014-01-24T12:18:10Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|name=RODA<br />
|purpose=RODA - Repository of Authentic Digital Objects<br />
|image=RODA-logo-basic.png<br />
|caption=RODA<br />
|alt=RODA<br />
|homepage=http://www.roda-community.org<br />
|license=LGPL v3<br />
|platforms=Linux, optimized for Ubuntu LTS releases<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Preservation System]]<br />
<br />
<br />
= Description =<br />
<br />
RODA is a digital repository created in conjunction with the Portuguese National Archives. Its primary objective is to allow long-term preservation and authenticity of digital objects of national importance. Based as much as possible on standards, following international specifications to become a trustworthy repository, as the OAIS/TRAC, and having high standards of security and scalability. The user interface was also an important consideration, as it was designed for archivists, producers, and consumers.<br />
<br />
= Features =<br />
<br />
RODA is a complete digital repository that delivers functionality for all the main units of the OAIS reference model. RODA is capable of ingesting, managing and providing access to the various types of digital content produced by large corporations or public bodies. RODA is based on open-source technologies and is supported by existing standards such as the OAIS, METS, EAD and PREMIS. <br />
<br />
* '''Conforms to open standards''' - RODA follows open standards using EAD for description metadata, PREMIS for preservation metadata, METS for structural metadata, and several standards for technical metadata (e.g. NISO Z39.87 for digital still images).<br />
* '''Vendor independent''' - RODA is 100% built on top of open-source technologies. The entire infrastructure required to support RODA is vendor independent. This means that you may use the hardware and Linux distributions that best fit your institutional needs.<br />
* '''Scalable''' - The service-oriented nature of RODA's architecture allows the system to be highly scalable, enabling the distribution of the processing load between several servers. Furthermore, new developments are in the works to enable RODA's preservation actions to be run over Hadoop clusters for even greater performance.<br />
* '''Embedded preservation actions''' - Preservation actions and management within RODA is handled by a task scheduler. The task scheduler allows the administrator to define the set of rules that trigger specific actions, and when these should take place. Preservation actions include format conversions, checksum verifications, reporting (e.g. to automatically send SIP acceptance/rejection emails), notification events, etc.<br />
* '''Authenticity''' - RODA uses preservation metadata (PREMIS) to create a trust chain between all format migrations and content verifications. The preservation metadata, together with the establishment of trust of its surrounding environment (ISO 16363) ensures reliability of the service and authenticity of the enclosed digital records.<br />
* '''Support for multiple formats''' - RODA is capable of ingesting and normalizing (according to the preservation plan in place) text documents, raster images, relational databases, video, and audio. A plug-in mechanism enables RODA to easily support additional formats.<br />
* '''Copes with the rapid changing nature of technology''' - The plug-in and task scheduling mechanism allows an easy way to add more functionality to the system (e.g. new preservation events, alerts, tools, etc.). Also, the service oriented architecture allows RODA base components to be incrementally updated, allowing a heterogeneous use of technologies at all levels: hardware, OS and applications.<br />
* '''Advanced access control''' - Users must be authenticated before accessing the repository. All user actions are logged for future accountability. Permissions are granular and can be defined at repository level, all the way down to individual data objects.<br />
* '''Integration with 3rd party systems''' - RODA exposes all its functionality via Web Services. Convenient Java libraries are available to allow developers to interact with RODA via its Core APIs. Several tools exist to create and manipulate the SIPs and submit them to RODA's ingest workflow.<br />
* '''Advanced ingest workflow''' - RODA supports the ingest of new digital material as well as associated metadata in 4 distinct ways: 1) online submission (self-archiving), 2) off-line submission using an client application called “RODA-in” (off-line self-archiving), 3) batch import by depositing SIPs via FTP or SMB/CIFS; and 4) integration with third-party document management software via invocation of SOAP Services or client API.<br />
<br />
<br />
<br />
<br />
= Development Activity =<br />
<br />
Code is being actively developed at [[https://github.com/keeps/roda RODA GitHub repository]]. Last version is RODA 1.2.0 (release at 2013-10-25) where the following new features were added:<br />
* Using Droid for file format identification<br />
* Added support for presentations: Microsoft Powerpoint (ppt, pptx), OpenOffice Presentation / LibreOffice Impress (odp)<br />
* Added support for spreadsheets: Microsoft Excel (xls, xlsx), OpenOffice Spreadsheet / LibreOffice Calc (ods)<br />
* Added support for email (.eml) but conversion is not yet supported<br />
* Added web service to download AIP<br />
* Added web service to download DIP<br />
<br />
<br />
For more information checkout the complete [[https://github.com/keeps/roda/blob/master/CHANGELOG.txt change log]].<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=Roda<br />
}}</div>Lfariahttps://coptr.digipres.org/index.php?title=File:RODA_logo_with-name.png&diff=1662File:RODA logo with-name.png2014-01-24T12:14:34Z<p>Lfaria: </p>
<hr />
<div></div>Lfariahttps://coptr.digipres.org/index.php?title=File:RODA-logo-basic.png&diff=1661File:RODA-logo-basic.png2014-01-24T12:12:35Z<p>Lfaria: Basic logo of RODA</p>
<hr />
<div>Basic logo of RODA</div>Lfariahttps://coptr.digipres.org/index.php?title=Roda&diff=1660Roda2014-01-24T12:03:00Z<p>Lfaria: </p>
<hr />
<div>{{Infobox_tool<br />
|name=RODA<br />
|purpose=An open-source digital repository designed for preservation<br />
|image=[[File:roda-logo.png|RODA]]<br />
|homepage=http://www.roda-community.org<br />
|license=LGPL v3<br />
|platforms=Linux, optimized for Ubuntu LTS releases<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Preservation System]]<br />
<br />
<br />
= Description =<br />
<br />
RODA is a digital repository created in conjunction with the Portuguese National Archives. Its primary objective is to allow long-term preservation and authenticity of digital objects of national importance. Based as much as possible on standards, following international specifications to become a trustworthy repository, as the OAIS/TRAC, and having high standards of security and scalability. The user interface was also an important consideration, as it was designed for archivists, producers, and consumers.<br />
<br />
= Features =<br />
<br />
RODA is a complete digital repository that delivers functionality for all the main units of the OAIS reference model. RODA is capable of ingesting, managing and providing access to the various types of digital content produced by large corporations or public bodies. RODA is based on open-source technologies and is supported by existing standards such as the OAIS, METS, EAD and PREMIS. <br />
<br />
* '''Conforms to open standards''' - RODA follows open standards using EAD for description metadata, PREMIS for preservation metadata, METS for structural metadata, and several standards for technical metadata (e.g. NISO Z39.87 for digital still images).<br />
* '''Vendor independent''' - RODA is 100% built on top of open-source technologies. The entire infrastructure required to support RODA is vendor independent. This means that you may use the hardware and Linux distributions that best fit your institutional needs.<br />
* '''Scalable''' - The service-oriented nature of RODA's architecture allows the system to be highly scalable, enabling the distribution of the processing load between several servers. Furthermore, new developments are in the works to enable RODA's preservation actions to be run over Hadoop clusters for even greater performance.<br />
* '''Embedded preservation actions''' - Preservation actions and management within RODA is handled by a task scheduler. The task scheduler allows the administrator to define the set of rules that trigger specific actions, and when these should take place. Preservation actions include format conversions, checksum verifications, reporting (e.g. to automatically send SIP acceptance/rejection emails), notification events, etc.<br />
* '''Authenticity''' - RODA uses preservation metadata (PREMIS) to create a trust chain between all format migrations and content verifications. The preservation metadata, together with the establishment of trust of its surrounding environment (ISO 16363) ensures reliability of the service and authenticity of the enclosed digital records.<br />
* '''Support for multiple formats''' - RODA is capable of ingesting and normalizing (according to the preservation plan in place) text documents, raster images, relational databases, video, and audio. A plug-in mechanism enables RODA to easily support additional formats.<br />
* '''Copes with the rapid changing nature of technology''' - The plug-in and task scheduling mechanism allows an easy way to add more functionality to the system (e.g. new preservation events, alerts, tools, etc.). Also, the service oriented architecture allows RODA base components to be incrementally updated, allowing a heterogeneous use of technologies at all levels: hardware, OS and applications.<br />
* '''Advanced access control''' - Users must be authenticated before accessing the repository. All user actions are logged for future accountability. Permissions are granular and can be defined at repository level, all the way down to individual data objects.<br />
* '''Integration with 3rd party systems''' - RODA exposes all its functionality via Web Services. Convenient Java libraries are available to allow developers to interact with RODA via its Core APIs. Several tools exist to create and manipulate the SIPs and submit them to RODA's ingest workflow.<br />
* '''Advanced ingest workflow''' - RODA supports the ingest of new digital material as well as associated metadata in 4 distinct ways: 1) online submission (self-archiving), 2) off-line submission using an client application called “RODA-in” (off-line self-archiving), 3) batch import by depositing SIPs via FTP or SMB/CIFS; and 4) integration with third-party document management software via invocation of SOAP Services or client API.<br />
<br />
<br />
<br />
<br />
= Development Activity =<br />
<br />
Code is being actively developed at [[https://github.com/keeps/roda RODA GitHub repository]]. Last version is RODA 1.2.0 (release at 2013-10-25) where the following new features were added:<br />
* Using Droid for file format identification<br />
* Added support for presentations: Microsoft Powerpoint (ppt, pptx), OpenOffice Presentation / LibreOffice Impress (odp)<br />
* Added support for spreadsheets: Microsoft Excel (xls, xlsx), OpenOffice Spreadsheet / LibreOffice Calc (ods)<br />
* Added support for email (.eml) but conversion is not yet supported<br />
* Added web service to download AIP<br />
* Added web service to download DIP<br />
<br />
<br />
For more information checkout the complete [[https://github.com/keeps/roda/blob/master/CHANGELOG.txt change log]].<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=Roda<br />
}}</div>Lfaria