HOW TO Load digital project images DEPRECATED DOCUMENT. Background:

Transcription

1 HOW TO Load digital project images DEPRECATED DOCUMENT Background: Images digitized in the context of a digital exhibition are loaded into the MCG01 (the non-escholarship) admin unit of DigiTool as an alternate delivery platform (and backup storage). Descriptive metadata is collected in the projectmetadata database. Once a record in this database has been approved it can be loaded into DigiTool. Metadata for images to be loaded is mapped to qualified Dublin Core and additional locally defined fields. Technical metadata is generated by the DigiTool ingest process. The DC.xml load file is generated by the projectmetadata database export tool. A record in the metadata file looks like this: <record xmlns:xsi=" xmlns:dcterms=" xmlns:dc=" <dc:creator>j.r.h.</dc:creator> <dcterms:localagentscantech>houston, Greg</dcterms:localagentscantech> <dc:description>photograph 45. One of a series of photographs assumed to be taken by John Hay.</dc:description> <dc:format>image/tiff</dc:format> <dc:identifier>045_ship_in_pack_ice_uncava_bay_labrador_photo</dc:identifier> <dc:language>eng</dc:language> <dc:publisher>rare Books and Special Collections, McGill University</dc:publisher> <dc:subject>ungava Bay (Québec)</dc:subject> <dc:subject>sailing ships </dc:subject> <dc:title>photograph of a ship in pack ice in Ungava Bay, Labrador by J.R.H.</dc:title> <dc:type>image</dc:type> <dcterms:localscandate> </dcterms:localscandate> <dc:extent>16.5 x 24 cm excluding borders</dc:extent> <dcterms:ispartof>lande Canadiana Collection</dcterms:isPartOf> <dcterms:localispartofexhibition>the Moravian Beginnings of Canadian Inuit Literature</dcterms:localispartofexhibition> <dcterms:spatial>ungava Bay (Québec)</dcterms:spatial> <dcterms:temporal>ca. 1900</dcterms:temporal> <dcterms:localcoveragetopical>introduction</dcterms:localcoveragetopical> <dcterms:localcallnid>photograph 45 Labrador Rare Books and Special Collections</dcterms:localcallnid> <dcterms:localmcgillnotes>rbsc Photograph collection - Box 22</dcterms:localmcgillnotes> <dcterms:localsubtype>image.photograph.black and white</dcterms:localsubtype> <dcterms:localfilename> ilename> <dcterms:localfilename> filename> <dcterms:localfilename> filename> <dcterms:localfilename> _photo.tif</dcterms:localfilename> <dcterms:localdcpidentifier>projectmetadata.item.493</dcterms:localdcpidentifier> </record> Note that 4 images are loaded for each record: the large image, the thumbnail, the medium (default) view and the archival tiff. 1

2 Ingest: Logon to and choose MCG01 as the admin unit. Click on the New Ingest Activity tab and fill in the ingest parameters as follows: Name: Something descriptive like <exhibition-name> image files is good. Ingest type: Dublin Core XML file and associated file stream(s). Scheduling: Use default settings to have the job run right away. Assign to: this should automatically show your login name. Note. Useful in the case that the person running the ingest is not the person who created it. Usually not used. Template Task Chain: Remote Stream Linkage 2

3 Click the Next > button Click on Technical Metadata Extraction in the All Tasks column in the left-hand panel and click the right arrow button (center of screen) to add it to the list of Scheduled Tasks in the right-hand panel. 3

4 Click the Next > button Parameters Digital Entity Template: dc_simple_entity_exhibitions.xml Processing Instruction File: dc_with_four_file_streams_ltma.xml DC file upload: use the Browse button to navigate to the location where you ve stored the metadata output file Remote Stream Download Store Link Locally: true Remote Stream Download File Extension: jpg,tif,tiff Technical Metadata File Extension: leave the defaults as is 4

5 Click the Next > button Upload Files File upload is not required because files will be loaded directly using the URLs provided in the metadata file. 5

6 Click the Activate button This activates the ingest. You can follow the progress of the ingest in the Folders tab by checking the number of jobs showing up next to the Scheduled, Running and Success (or Failed) folder tabs in the left-hand column. If the upload succeeded, the completed job will show up at the top of the list in the Success folder, as shown above. Click on the ingest id (e.g. ing2054) in the Id column. 6

7 This will display a list of the uploaded items in a separate window. Check that the icons in the Delivery column are all JPG or TIFF icons ( ). In some circumstances objects may show up either as web icons or unknown ( ), which means the ingest failed to correctly associate a mime type with the file object. If this happens, follow instructions for failed jobs, below. Note that each image has four manifestations: a VIEW, THUMBNAIL, VIEW_MAIN (all jpegs) and ARCHIVE (tif). 7

8 Failed jobs: If a job shows up in the Failed jobs folder, or if a successful job failed to correctly associate the correct mime type with the file objects, highlight the ingest job by clicking on its name in the list of jobs, click on the Full/Split Mode icon ( ) at the top of the list of jobs and then click the Task Log tab in the Log View: pane which will appear in the lower portion of the screen. This will display the ingest job log which can help track down why an ingest failed. For example, if there were errors in the metadata load file, they will be listed here. Click the ingest rollback icon ( ) to rollback the ingest. This removes any objects which might have been created before the job failed. The job will now show up in the Not Scheduled folder. Click on the edit icon ( ) to verify and adjust all ingest parameters and to re-upload a corrected metadata file, if required. Click on the Save button at the bottom right of the screen, move to the Upload step and click the Finish button at the bottom right of the screen. The job will be moved to the Scheduled jobs folder. Click the Activate icon ( ) to rerun the job. 8

9 Post ingest: After the ingest has been completed, the pathtofile field in the projectmetadata database needs to be updated to point to the VIEW_MAIN image loaded into DigiTool. This is necessary so that the local project-shares directory for the project on dasheng (the development server) can be emptied in order to make space for other project files. 9