Here you can find a description of the steps involved in the SCALA workflow. These steps allow you to transfer archival data into SIPs, then into AIPs and finally have them stored on disk for permanent storage.
| What | Get your archival data and export it to your computer. |
| How | Arrange your digital born files into comprehensive units of archival data (such as series/files/items/...). For each such unit, we will later on create a SIP. You can go as granular as you wish, and there can be parent-child relations between SIPs. Each unit of archival data must be exported into its own separate folder on your computer. |
| Where | Your archival data are probably on the original carriers, or on temporary storage space. |
| What | Prepare descriptive metadata for each SIP. |
| Why | Descriptive metadata will help make sure you can look up and retrieve the content of your SIPs in later stages. The more details given, the better. Examples of descriptive metadata fields are title, creator, producer, scope & content, release date, ... |
| How | From you archive management system, export descriptive metadata into an XML file per SIP. There are international standards with naming and structuring definitions for the fields in these XMLs. EAD 2002 and Dublin Core are famous examples you can adhere to. Otherwise simple key-value pairs work as well. If there is no descriptive metadata available in your archive management system, you will have to type it yourself into an XML file per SIP (which can be a time consuming process). |
| Where | Ideally you can export this data as an XML per SIP from your archive management system. Otherwise you will have to create the XMLs yourself. |
| What | Create E-ARK2 SIPs by combining archival data and their respective descriptive metadata in structured way. |
| How | RODA-In is our recommended SIP creation tool. Use it to select your data folders and automatically match descriptive metadata. Then you can make representation edits and add extra documentation if needed. Lastly generate E-ARK2 structured SIPS, with METS file and representations. |
| Where | You can download the latest RODA-In version here. |
RODA-In.mp4
| What | Upload SIPs to a dedicated SFTP server using an FTP client. |
| Why | Once uploaded to the server, the RODA tool can automatically start ingesting the SIPs and transform them into AIPs. |
| How | Download an FTP client and connect to the server. Upload SIPs and mark them as 'ready for ingestion by RODA'. |
| Where | Any FTP client you can find online should work, such as WinSCP. Contact a server administration at meemoo to get the required connection details for the server. |
FTP.SIP.upload.mp4
| What | Transform uploaded SIPs into AIPs in RODA. |
| How | Automatically! SIPs on the SFTP server are picked up and go through an AIDA ingest workflow where several plugins do checks and transformations on the SIP. This results in an E-ARK2 AIP if no issues were found. |
| Where | The ingest process can be tracked on the RODA process tab. You will need to request RODA login credentials with your organization. |
RODA-AIDA-ingest-workflow.mp4
RODA executes the following plugins in order during the AIDA ingest workflow. Plugins are mandatory or optional. If an issue is raised by a mandatory plugin, the ingest of the AIP will fail and you will need to fix the issue before trying again. Optional plugins will not break the ingest procedure when there is an issue; however you can later still try to address and fix the issue in RODA.
- E-ARK SIP2 to AIP - Checks if the SIP is well formed, complete and that no unexpected files were included in accordance with the commons IP E-ARK validator tool.
- Remove unwanted files - A blacklist is maintained with useless file formats that are automatically extracted from the SIP. This blacklist can be expanded if necessary.
- Antivirus - Scans information package(s) for malicious content using the antivirus application ClamAV. If malicious software is detected, a report is generated and a PREMIS event records this action.
- Descriptive metadata validation - Checks that descriptive metadata exists in the information package and that it is valid according to the XML Schemas (XSD) installed in the repository. A validation report is generated indicating which information packets have valid and invalid metadata.
- Fixity information computation - Calculates the file fixity information (also known as checksum) for all data files within an AIP, representation, or file and stores this information in PREMIS objects. Three checksums are calculated based on the following algorithms: SHA-256, SHA-1 and MD5.
- File format identification (Siegfried) - Identifies the file format and version of data files contained in information packages using the Siegfried tool. Like DROID, Siegfried identifies files based on digital file signatures stored in the PRONOM database. The job updates the PREMIS object metadata in the information package to store the format identification results. A PREMIS event is logged after the task is executed. Siegfried configuration information.
- Verify user authorization - Checks whether the user has sufficient rights to ingest AIPs for the organization.
- Generate meemoo descriptive metadata - Create a meemoo.xml file with descriptive metadata detailing the synchronization status with meemoo MAM.
| What | Edit AIPs in RODA and mark them for long-term storage. |
| How | In the RODA catalogue you are able to find and inspect all your AIPs. You can update the content of data representations or descriptive metadata, or run new process plugins on your AIPs.  These actions result in PREMIS events which are added to the AIPs.  When you are done, you can mark your AIPs for long-term storage. |
| Where | All this can be done in the RODA Catalogue of your organization. You can use it to search, select and edit AIPs. |
Edit-AIPs-in-RODA.mp4
| What | Select AIPs to be stored long-term on the meemoo MAM. |
| How | Select all AIPs you wish to store. Then start the 'Submit AIP to meemoo' plugin. The AIPs will then be submitted to the meemoo MAM, alongside with a sidecar.xml file containing essential descriptive metadata to ensure searchability in MAM. You can follow the progress of this job in RODA. Each AIP will have meemoo metadata present in RODA. This metadata details the synchronization status with MAM.  After the AIPs have been safely stored on the MAM, you can choose to remove the data representations in RODA. This way, you keep working memory available in RODA for new processes. The metadata will remain in RODA however, allowing you to keep using its search engine for looking up AIPs. The process of removing data representations is called pruning, and it can be reversed by restoring data from MAM to RODA using 'unpruning'.   |
| Where | All this can be done in the RODA Catalogue of your organization. Simply select the AIPs you want to submit to MAM, prune or unprune. Then execute the desired plugin. |
| Video example | Coming soon! |
| What | Retrieve AIP representation data from MAM to RODA and make updates to it. |
| How | Select the 'restore pruned representations from meemoo' process and execute it on AIPs to restore their data representations. During this process, the following plugins will be run on the restored AIPs: fixity information computation, file format identification (Siegfried) and antivirus. You can then further edit the data or run other plugins on it. |
| Where | All this can be done in the RODA Catalogue of your organization. Select the AIPs you want to retrieve data representations from and then execute the 'restore pruned representations from meemoo' plugin. |
| Video example | Coming soon! |
| What | Confirm that your AIPs are stored in the MAM. |
| How | Log into the MAM site and search for your AIPs using the search bar. |
| Where | You can log into the MAM here. Request user credentials via your meemoo contact. |
| Video example | Coming soon! |