The last step in the SIP creation process is to export the mapped SIPs to an output format to be submitted to the repository for ingest. It’s important to note that RODA-in does not check if the SIPs are valid before exporting them and this process should be performed on the repository or with an external tool.
You can personalize the export process to be tailored to your needs. The first decision is whether to export all the SIPs present in the classification plan or only the selected ones. By default, the only exported SIPs are the selected items when the user clicks the “Export” button, but that can be overriden using the “Export all” toggle button. Another required field is the destination of the SIPs once they’re exported. It’s also at this stage that the export format/type ust be chosen, at the moment, RODA-in supports two\: E-ARK SIP and BagIt.
+fileExplorer=An item can be in one of three states\: normal, ignored or mapped. Normal is the default state of the items and the only state from which SIPs can be created.
Items in the ignored state will not be used to create packages. They can be ignored based on rules defined in the configuration of the application, or manually using the “Ignore” button. These items are hidden by default, but can be made visible by turning on a menu option.
Mapped items are the ones that have already been added to an SIP. The goal is to implement a “map and forget” strategy in which users drag n’ drop items from their file system to create SIPs after which they disappear from the user interface. This enables users to fully focus on the remaining items and thus be more productive in their SIP creation project.
+firstStep=The first step of the workflow is to choose which computer files and folders to archive and add them to the application’s file explorer. This action will display the folder and its content in a folder tree structure. The folders and files are clearly distinguishable from each other (since their icons are different) and folders can be expanded in order to inspect its children elements. +inspectionPanel=After creating SIPs, you can opt to manually enrich the SIPs or handle exceptional cases manually. This is an optional step, nevertheless it contains some important features that should not be overlooked such as creating and validating metadata, manipulating the SIP's content or adding documentation. +inspectionPanel.associations=The associations panel displays the association rules that have the current selected node as the output. Each rule displays the input items, the aggregation option used to create the SIPs and how many SIPs were created. Additionally, the user may also remove the SIPs created by the rule by clicking the "Remove" button. +inspectionPanel.data=The SIP’s data (or content) is divided in “representations” which can be added or removed. Removing files and folders from the SIP content is also possible. These files will return to the normal state and will become available in the file explorer to be included in another SIP. The drag n’ drop system of the data folder structure enables rearranging the content of the SIP and moving files between representations. Clicking the rightmost button changes the panel between “Data” and “Documentation”.
Documentation can be added to SIPs to complement the information that is being archived in the Data section. Files and folders can be added from the application’s file explorer or from the operation system’s file explorer using a drag and drop system. Unlike when files are added to the Data section of SIPs, adding documentation does not set the state of the files as mapped, so the producer can add the same file to the documentation of any number of SIPs. After being added, the files can be removed and rearranged in the same way as in the Data section.
+inspectionPanel.metadata=When SIPs are created using the metadata template option, you are able to edit metadata via an input form. Additionally, the XML source of the metadata file can also be displayed and edited on the user interface. In addition to editing metadata files, it’s possible to add and remove metadata files. There are three options available when adding a new metadata file\:
To avoid conflicts, two metadata files of the same description item cannot have the same name, so new files are rejected if this happens. As a consequence of this, two files based on the same template cannot be present in the same description item.
Provided that the schema is added to the type definition, RODA-in provides another useful feature\: metadata validation. This feature is only available to metadata files created from templates and the template’s type must have a schema correctly added in the configuration. In the case where a user is editing a form, with the push of a button the tags from the template are temporarily replaced with the corresponding values and the resulting file is validated against the schema. If the file cannot be validated successfully, the application displays a detailed error message and the location of the error, otherwise it only shows a success message.
+link.associate=Asociar +link.associationMethod=Association method +link.export=Exportar +link.fileExplorer=FileExplorer +link.firstStep=Creating SIPs\: first step +link.inspectionPanel=Inspection panel +link.inspectionPanel.associations=Inspection\: Associations +link.inspectionPanel.data=Inspection\: Data / Documentation +link.inspectionPanel.metadata=Inspection\: Metadata +link.metadataMethod=Metadata method +link.schemaPane=Classification scheme +link.secondStep=Creating SIPs\: second step +link.templatingSystem=Templating system +metadataMethod=SIPs may contain data and metadata. The metadata is included in each SIP by means of association rules. These association rules define how descriptive metadata selected from the file system is included inside each SIP. There are currently four available metadata association options. +schemaPane=To create a classification plan, the first step is to add description items using the Add button present at the bottom of the central panel. When the button is pressed, a new description item is created and appended under the selected description item or under the root if no description item is selected or the selected item is a SIP.
The removal process starts by selecting the items we wish to remove and clicking the Remove button, available at the bottom of the panel. Any selected SIPs are removed and its contents return to the normal state, so that they can be added to other SIPs. When a description item is removed, all its descendant SIPs are also removed.
By dragging and dropping selected items on top of other items, the classification scheme can be completely re-organized. The behaviour of the drag’n’drop system is described as follows\:
After the classification scheme is completed, you may opt to save it for later use using the “Export” menu option which can be found under the Classification Scheme menu. Lastly, the footer displays information about the selected item\: the number of SIPs, folders, files and size.
+secondStep=The classification scheme can either be imported from file or created directly in the application. In the first option, the user must import a JSON formatted file which was either exported by RODA or RODA-in, since these are the only supported formats at the time. To create a classification plan, the first step is to add description items using the "Add" button present at the bottom of the central panel. When the button is pressed, a new description item is created and appended under the selected description item or under the root if no description item is selected or the selected item is a SIP. In addition to adding items, there are two other actions available, removal and organization. +templatingSystem=Since it's tedious to edit the template files by hand, we added a way to create forms based on the fields of the templates. These files are located in the "roda-in" folder (My Documents when using Windows and the user's home directory if using Unix), under the "templates" folder. Using the powerful Handlebars engine, anyone can create template files with the necessary information to create the form. In addition to a simple tag, (e.g. {{person}}), we can now add options which will modify the way each field is created. These options are key-value elements, e.g. title\="SIP creation using RODA-in", where the key is the name of the option and the value is the value that will be given to that option. Only the first tag should have options, i.e., if there's two tags with the same name, the options of the second are ignored. The options are not required, the form is still created with a simple tag, which creates a simple text field.
The available options that alter the fields created for each tag are\:
type\="list". The format is a JSON array. Example\: [option A, option B, "option C"]The following is an example of how the tags can be used\:
{{title order\=1 type\="text" label\="Template title" mandatory\=true auto-generate\="title"}}