Content Comparison

...

1. At least one dedicated repository contact. 
2. A CoA code to be used for all fill orders by default if the repository wants to use “fill order” option. 
3. A set of default DRS related values:  
   1. Image File Format to deposit (we strongly recommend Lossless JPEG2000)  
   2. DRS Owner Code 
   3. DRS Billing Code 
   4. DRS Access Flag 
   5. DRS UNR mask 
   6. DRS reports recipient emails

4.Where to share DRS related information for each order? 

1. Add as note to the Aeon order (for simple instructions) 
   1. Attach to Aeon orders  
      1. For PDS objects spreadsheet or still image objects filename instruction 
      2. Limit: Aeon only allows having one file attached for each order) 
   2. Save to a shared space (limit: to have a shared space) 
      1. For PDS objects spreadsheet or still image objects filename instruction 
      2. Limit: Need a shard space (IS or Department shared space, SharePoint) 
      3. Extra: well managed structure to ensure easy locating the files 
   3. Email attachments 
      1. For PDS objects spreadsheet or still image objects filename instruction 
2. Who will add NET holdings in ALMA?  
   1. Repository, or 
   2. Imaging Services: IS only adds ALMA NET holding, see Add ALMA NET holding section for details. If repositories would like IS to use a specific template for a certain type of deposits, please let us know. 
3. Who will send patrons URNs if the requests are delivered as online URNs? 
   1. Repository, or 
   2. Imaging Services 

For each order 

For each order, the repository needs to provide the following information based on the object type to be deposited into DRS. The information can be entered in a note or attached as a file to the Aeon order. If a PDS or Still Image object spreadsheet is used, the information can be included in the first row of the sheet. If the information is shared in a file, please include the Aeon Transaction number in the filename. 

...