This page describes the process for digitizing and importing a score using the djvu standalone encoder bundled with Variations.
Before digitizing a document determine what Cataloging ID will be given to the document. Each institution will should have a predetermined Cataloging ID scheme (filenaming) for naming records. If a Cataloging ID does not exist for the document that is being ingested one will need to be created.
For more information on Cataloging ID visit the Cataloging ID and System ID page.
There are Four ways to add files to the Encode List:
Adding a directory to the Encode List will add all files in that directory or beneath that directory except Thumbs.db. If you attempt to add a file that already exists in the list with the same specified output file, it will be skipped without warning.
Click the Encode button to start encoding the files in the Encode List. If a file already exists at the specified output location, a warning dialog will ask if you want to overwrite the preexisting file. Files that have already been successfully encoded and are still in the Encode List will be skipped unless their status has been reset by selecting the file, right-clicking the mouse, and clicking Reset File Status.
To stop the current and all subsequent files from being encoded by the current encoding process, click the Stop button.
To remove all files from the Encode List either click Clear All or right-click in the Encode List and click Clear All Files.
To remove one or multiple files, select the file(s), right-click the mouse to bring up the popup menu, and click Remove File.
To reset the status of one or multiple files, select the file(s), right-click the mouse to bring up the popup menu, and click Reset File Status. The tooltip text for these files should read Unprocessed after doing this.
To set the Default encoding profile, use the drop down box below the Encode button. The Default encoding profile will be applied to files as they are added to the Encode List, but will not change the encoding profile for files already added to the list.
By default pages are set to the Default encoding profile when they are added to the Encode List. To set a page's encoding profile, select the file, right-click, and select the appropriate encoding profile from the Set Profile menu.
This step can be skipped if the standalone encoder has been set to save the derivative files to the incoming directory.
After pages are added into the system the digitizer interface will display the pages in the Structure window. When a page is added it is placed in a tree structure based on the file's name. The structure window aids the digitizer in ordering, grouping, moving, deleting, and generally structuring the document to match the physical document's structure. Displaying the structure of the document not only aids the digitizer, but also gives information to the end user about how the score is structured. The structural metadata allows users to jump to important pages, navigate the score, and generally ascertain information about how the score is structured.
How information is represented to end-users
After a page has been added it may not be in the correct location or may need to be removed. Variations allows for pages to be moved, reordered, or deleted.
The moving option allows pages to be moved between groupings and between grouping and non-groupings.
Ordering allows files to be moved into the correct location. Since the pages are ordered by their page number Variations must renumber the pages to reorder them. If the pages are named correctly Variations should order them correctly, while ordering offers the opportunity to correct errors.
Since larger scores or collections of scores may include multiple books, Variations allows the score to be divided into volumes. Similar to CD sides for audio media, volumes allow the system to express information to the user about how the score is physically structured. Volumes cannot be created though the Variations interface and instead must be specified through the naming of the files. Ideally volumes will be specified when the files are first digitized and named. If the files are given the appropriate name (i.e. filename-01-001, ...), Variations will display the pages in their correct locations and create the necessary number of volumes.
When an entire score belongs to a single volume, Variations requires that the file still be named to denote that all of the pages are part of volume one. Variations will not add pages that do not have a volume number associated with them or if the volume is 00.
If there is a need to create multiple volumes at a later time, the pages would have to be removed and re-added following the appropriate naming convention.
Example of a single volume score in Digitizer Window:
Labeling pages aids users in navigating and selecting pages from the score view window. Pages can be labeled numerically or labeled individually to give more information. Labeling pages does not require syncing with the tiff files and can only be done from the digitizer interface.
Grouping pages is a good way to give the user more information about the structure of the score or to highlight important grouping of pages. Grouping pages does not require syncing with the tiff files and can only be done from the digitizer interface.
Example of Grouping and Labeling
Grouping & Labeling at IU
The application of tools like grouping and labeling may vary between institutions. To see IU's process for labeling and grouping pages, visit the Score Container Structure Guide .
Diacritics and other special characters can be entered by hitting the F2 key.
After entering all the metadata, click Save or Save & Exit. Saving the record may take some time because Variations checks to make sure all the pages are in the proper order and renames files sequentially. If Variations finds the derivative files on the server, it processes them and moves them to their serving location in the score-objects directory on the server. When a file is saved it is only visible to other catalogers and digitizers. The file can still be edited and changed at a later period of time.
If the files process correctly, the status in the Digitizer window should change to This record is valid, and the item should show up as "ready to Publish" in the progress listing on the digitizer tab in the Search window. Pressing the "Publish" button lets the system know that, when the nightly cron job is run, this score should be moved from the cataloging server to the production server.
When a file is ingested and saved in Variations, the record is created on the cataloging server and is only available to digitizers and catalogers. Once the file is published it is moved to the production server it is available to the end-users. This process prevents end-users from encountering partially digitized, incomplete, or incorrect records.