All Projects → keeps → roda

keeps / roda

Licence: other
RODA - Repository of Authentic Digital Objects

Programming Languages

java
68154 projects - #9 most used programming language
HTML
75241 projects
XSLT
1337 projects
Handlebars
879 projects
javascript
184084 projects - #8 most used programming language
CSS
56736 projects

Projects that are alternatives of or similar to roda

mik
The Move to Islandora Kit is an extensible PHP command-line tool for converting source content and metadata into packages suitable for importing into Islandora (or other digital repository and preservations systems).
Stars: ✭ 32 (-40.74%)
Mutual labels:  migration, digital-preservation, digital-repository
IFIscripts
Detailed documentation is available here: http://ifiscripts.readthedocs.io/en/latest/index.html
Stars: ✭ 46 (-14.81%)
Mutual labels:  metadata, digital-preservation, premis
action-sync-node-meta
GitHub Action that syncs package.json with the repository metadata.
Stars: ✭ 25 (-53.7%)
Mutual labels:  metadata, repository
brunnhilde
Siegfried-based characterization tool for directories and disk images
Stars: ✭ 55 (+1.85%)
Mutual labels:  archives, digital-preservation
metadata-qa-marc
QA catalogue – a metadata quality assessment tool for library catalogue records (MARC, PICA)
Stars: ✭ 59 (+9.26%)
Mutual labels:  metadata, catalogue
hasura-metadata-patcher
CLI tool to patch Hasura metadata json file. Helps to organize complex CI/CD flows through different environments.
Stars: ✭ 14 (-74.07%)
Mutual labels:  metadata, migration
islandora vagrant
Islandora testing and development environment
Stars: ✭ 36 (-33.33%)
Mutual labels:  metadata, preservation
astlinux
AstLinux is a "Network Appliance for Communications" x86_64 Linux distribution
Stars: ✭ 23 (-57.41%)
Mutual labels:  sip
mumsi
SIP to Mumble gateway/bridge using PJSUA stack.
Stars: ✭ 33 (-38.89%)
Mutual labels:  sip
TEAM
The Taxonomy for ETL Automation Metadata (TEAM) is a metadata management tool for data warehouse automation. It is part of the ecosystem for data warehouse automation, alongside the Virtual Data Warehouse pattern manager and the generic schema for Data Warehouse Automation.
Stars: ✭ 27 (-50%)
Mutual labels:  metadata
timber-ruby
🌲 Great Ruby logging made easy.
Stars: ✭ 155 (+187.04%)
Mutual labels:  metadata
nginx-auth-cas-lua
CAS authentication for nginx, similar to apache mod-auth-cas
Stars: ✭ 20 (-62.96%)
Mutual labels:  cas
git-repo-name
Get the repository name from the git remote origin URL
Stars: ✭ 21 (-61.11%)
Mutual labels:  repository
awesome-starless
A curated list of awesome repositories with few stargazers but has a huge users.
Stars: ✭ 38 (-29.63%)
Mutual labels:  repository
gutenberg-metadata
Metadata from Project Gutenberg
Stars: ✭ 24 (-55.56%)
Mutual labels:  metadata
aip-go
Go SDK for implementing resource-oriented gRPC APIs.
Stars: ✭ 47 (-12.96%)
Mutual labels:  aip
cas-management
Apereo CAS Management Web Application
Stars: ✭ 40 (-25.93%)
Mutual labels:  cas
Yuna
Yuan企业通用后台,快速实现微后台架构
Stars: ✭ 19 (-64.81%)
Mutual labels:  cas
skyrimse
The TES V: Skyrim Special Edition masterlist.
Stars: ✭ 99 (+83.33%)
Mutual labels:  metadata
replica
Replica, the id3 metadata cloner
Stars: ✭ 13 (-75.93%)
Mutual labels:  metadata

CI Join the chat at https://gitter.im/keeps-roda/community

RODA - Repository of Authentic Digital Objects

RODA is a digital repository solution 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 objects produced by large corporations or public bodies. RODA is based on open-source technologies and is supported by existing standards such as the Open Archival Information System (OAIS), Metadata Encoding and Transmission Standard (METS), Encoded Archival Description (EAD), Dublin Core (DC) and PREMIS (Preservation Metadata).

Features

  • User-friendly graphical user interface based on HTML 5 and CSS 3
  • Digital objects storage and management
  • Catalogue based on rich metadata (supports any XML-based format as descriptive metadata)
  • Off-the-shelf support for Dublin Core (DC) and Encoded Archival Description (EAD).
  • Configurable multi-step ingestion workflow
  • PREMIS 3 for preservation metadata
  • Authentication and authorization via LDAP and CAS (support for additional authentication methods)
  • Reports and statistics
  • REST API
  • Pluggable preservation actions
  • Integrated risk management
  • Integrated format registry
  • Uses native file system for data storage for greater performance and transparency
  • 100% compatible with E-ARK SIP, AIP, and DIP specifications
  • Support for design themes
  • Retention and disposal schedule support

For more information, please feel free to visit the RODA website: http://www.roda-community.org

Documentation

RODA is provided with a series of documentation articles that are constantly being updated. You may find all the available documentation here.

All documentation articles are written in markdown, which means that you can easily converted to various formats such as PDF, HTML, etc. Check this online tool that converts markdown to PDF: http://www.markdowntopdf.com.

Installation

We provide installation methods for testing and production environments for several different operating systems. For more information on the installation process, please visit our documentation page.

Usage

After installing, direct your browser to the correct IP address (this depends on your installation mode and used settings) and log in with the following credentials:

  • Username: admin
  • Password: roda

With these credentials you will have access to all features.

Then you can start using RODA. Here's an example of what you can do:

  1. Go to Catalogue and click the button NEW, select Dublin Core and fill the title of your new collection.
  2. Go to Ingest > Transfer and upload files (e.g. PDF) or SIPs made by RODA-in. SIPs will have metadata while PDFs wont. To know how to use RODA-in watch the tutorials.
  3. After upload, select the SIPs or files to ingest on the checkbox and click the button PROCESS on the sidebar under the section Ingest.
  4. Now configure the ingest workflow, select the SIP format, if you upload a file select Uploaded file/folder, if you uploaded a SIP select the SIP format (E-ARK or BagIt).
  5. Under the Parent Object you can select the new collection you created above.
  6. After configuring ingest click the CREATE button.
  7. Now ingest will start and you can see the status of it at Ingest > Process, you can also inspect the status by clicking the table row.
  8. When finished you can go to Catalogue or Search to find your new ingested content.

Developers

To start developing new components for RODA check the Developer guide which has information on:

  • How to get the source code
  • How to build and run
  • How to set up the development environment
  • Code structure
  • How to contribute
  • etc.

Browser compatibility

Testing RODA on different browsers is done in an easy way thanks to BrowserStack!

BrowserStack website

Translators

Translations are maintained in Transifex and updated using the Transifex Client.

Check our Translation guide for more information.

Specifications

RODA implements a series of specifications and standards. To know more about the OAIS Information Packages that RODA implements, please check out the Digital Information LifeCycle Interoperability Standards Board repositories on GitHub at https://github.com/dilcisboard.

Professional Support

We’re committed to providing the highest standard of service that empowers you to succeed in preserving your digital assets, on premises, in the cloud or anywhere in between.

Professional Support is available as a single “pay-per-incident” (PPI) or annual support service. Professional Support incidents focus on troubleshooting a specific problem, error message, or functionality that is not working as intended. An incident is defined as a single support issue and the reasonable effort to resolve it. Incidents should be submitted online. Response time will be between 2 and 8 days, depending on severity of incident.

For more information and commercial support, please contact KEEP SOLUTIONS.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].