Digital Assets Module Services adam-01 and adam-02 versions 17 and up Presenter: Yoel Kortick

Introduction ALEPH offers various batch services to import and export digital objects and metadata. While descriptive metadata (bibliographic) is stored as part of the bibliographic record (Z00), the technical metadata is stored in its own Oracle table (Z403). Both import and export are based on XML files that contain specific sections for descriptive metadata and technical metadata. To upload objects into the system, usually, you need to run two services (adam-01 and adam-02). Both are part of the services menu:

Accessing the services

Running the services We will describe and show a situation here where A library has seven jpg files for which they want to create an xml file Adam-01 will be run to create the xml file Adam-02 will be run to upload the xml file and thereby create a bibliographic record and object link for each jpg file

Create Digital Objects Upload File (adam-01) This service is used to create an XML file that is required to upload files into the system that do not have descriptive metadata (bibliographic records) or technical metadata (Z403). The XML file created by this service contains descriptive and technical metadata generated by using a template (z403_template.xml) that has to be manipulated by the user. The XML file created by this service can be taken to load objects and metadata into the system using the adam-02 service.

Sample xml template A sample XML template to be edited by the user can be found in the tab directory of USM01. The XML file contains different sections for descriptive (<record>) and technical metadata (<z403>). The following is an example of the XML file: il-aleph02-18(1) USM01-YOELK>>cd $data_tab il-aleph02-18(1) USM01-YOELK>>ls -lrt z403_template.xml -rw-rw-r-- 1 aleph exlibris 2722 Nov 18 2005 z403_template.xml

The xml files When adam-01 is run, another XML file is generated that contains the descriptive and technical metadata and a relative path to the digital objects. This XML file has the same name as the directory it is in, plus the xml file extension. For example, if the directory that contains the objects and the template is named nature, the XML file resulting after adam-01 has been run will be nature.xml. This XML file can be used for the actual upload with the service adam-02.

The xml files Note that the XML file will contain the digital object’s filename as title if no explicit title is specified in the <record> section of the template. The No. of Created Bibliographic Records parameter determines the number of bibliographic records that will be created. The "One record per object" option creates a metadata record (in other words a bibliographic record) for each digital object. The "Single record for all objects" option creates a single metadata record for all digital objects processed by the service.

The adam-01 interface

Input directory Type here the name of a directory that includes digital objects and an XML template. This input directory must be under the local library's import directory (for example, /exlibris/aleph/a18_1/usm01/import_files). Thus if the actual directory is: /exlibris/aleph/a18_1/usm01/import_files/bradies/ Put this in the “input directory” field: bradies

Report file name Enter the name of the report file, which will contain the list of records that were rejected by system.

No. of created bibliographic records Determines the number of bibliographic records that will be created. Select the "One record per object" option if you want to create a metadata record (in other words a bibliographic record) for each digital object. Select the "Single record for all objects" option, if you want to create a single metadata record for all digital objects processed.

Example In the import directory “bradies” we have seven jpg files and the required xml template “z403_template.xml”. il-aleph02-18(1) USM01-YOELK>>cd $usm01_dev/usm01/import_files/bradies/ il-aleph02-18(1) USM01-YOELK>>pwd /exlibris/aleph/a18_1/usm01/import_files/bradies il-aleph02-18(1) USM01-YOELK>>ls -lrt total 32 -rw-rw-r-- 1 aleph exlibris 2602 Oct 26 12:25 alice_the_maid.jpg -rw-rw-r-- 1 aleph exlibris 2192 Oct 26 12:25 bobby_brady.jpg -rw-rw-r-- 1 aleph exlibris 2291 Oct 26 12:25 brady_children.jpg -rw-rw-r-- 1 aleph exlibris 2301 Oct 26 12:25 cindy_brady.jpg -rw-rw-r-- 1 aleph exlibris 1744 Oct 26 12:25 greg_brady.jpg -rw-rw-r-- 1 aleph exlibris 1642 Oct 26 12:26 marsha_brady.jpg -rw-rw-r-- 1 aleph exlibris 3937 Oct 26 12:26 the_brady_bunch.jpg -rw-rw-r-- 1 aleph exlibris 2722 Oct 26 12:26 z403_template.xml

Example We then run the service as follows:

Example A new xml file is created with the name of the directory plus an xml extension: il-aleph02-18(1) USM01-YOELK>>ls -lrt total 56 -rw-rw-r-- 1 aleph exlibris 2602 Oct 26 12:25 alice_the_maid.jpg -rw-rw-r-- 1 aleph exlibris 2192 Oct 26 12:25 bobby_brady.jpg -rw-rw-r-- 1 aleph exlibris 2291 Oct 26 12:25 brady_children.jpg -rw-rw-r-- 1 aleph exlibris 2301 Oct 26 12:25 cindy_brady.jpg -rw-rw-r-- 1 aleph exlibris 1744 Oct 26 12:25 greg_brady.jpg -rw-rw-r-- 1 aleph exlibris 1642 Oct 26 12:26 marsha_brady.jpg -rw-rw-r-- 1 aleph exlibris 3937 Oct 26 12:26 the_brady_bunch.jpg -rw-rw-r-- 1 aleph exlibris 2722 Oct 26 12:26 z403_template.xml -rw-rw-r-- 1 aleph exlibris 22414 Oct 26 12:29 bradies.xml This file may now be uploaded via adam-02.

Example Here is the file bradies.xml as created by ALEPH: <?xml version="1.0" encoding="UTF-8"?> <file> <record xmlns="http://www.loc.gov/MARC21/slim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"> <leader> nam a 4500</leader> <controlfield tag="008"> b 000 und d</controlfield> <datafield tag="100" ind1="0" ind2=" "> <subfield code="a">Creator from template</subfield> </datafield> <datafield tag="650" ind1=" " ind2="0"> <subfield code="a">Topical term from template</subfield> <datafield tag="245" ind1=" " ind2=" "> <subfield code="a">alice_the_maid.jpg</subfield> </record> <z403>

Example We can edit it as follows: <?xml version="1.0" encoding="UTF-8"?> <file> <record xmlns="http://www.loc.gov/MARC21/slim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"> <leader> nam a 4500</leader> <controlfield tag="008"> b 000 und d</controlfield> <datafield tag="100" ind1="0" ind2=" "> <subfield code="a">Smith, James</subfield> </datafield> <datafield tag="650" ind1=" " ind2="0"> <subfield code="a">Brady bunch TV series</subfield> <datafield tag="245" ind1=" " ind2=" "> <subfield code="a">Alice the maid</subfield> </record> <z403>

Import records and digital objects (adam-02) This service takes the XML file generated with adam-01 or any other XML file with appropriate format and content and runs the upload into the system. This service creates records in Z00 (bibliographic) and Z403 (technical metadata) according to the definitions in the XML file. Note that the XML file to be loaded is required to have the same name of the directory plus the xml file extension, otherwise it will not be loaded. If the file was created via adam-01 it will already have this format.

Import records and digital objects (adam-02) Note in addition that if the Z403-TITLE field is not filled, the system takes the content of Z13-TITLE instead. The Z13 record is automatically created during the load of the descriptive metadata (Z00) according to standard configuration (tab22). You can upload digital objects to existing bibliographic records without changing the descriptive metadata (bibliographic). To do this, edit the XML file generated with adam-01 or delivered in an appropriate format and leave all field tags in the <record> section empty and add the following line to the <record> section in the template.

Import records and digital objects (adam-02) <controlfield tag “SYS”>NNNNNNNN</controlfield> NNNNNNNNN is a variable for the record’s system number. For example, <controlfield tag “SYS”>000050018</controlfield> will upload objects to the bibliographic record #000050018. Note that if the system number does not exist in the catalog, no objects will be uploaded.

Import records and digital objects (adam-02) We run the service as follows:

Import records and digital objects (adam-02) In $alephe_scratch a file “bradies_numbers” is created which includes the system numbers of the new records il-aleph02-18(1) USM01-YOELK>> >>cat $alephe_scratch/bradies_numbers 000050316USM01 000050317USM01 000050318USM01 000050319USM01 000050320USM01 000050321USM01 000050322USM01 We have one system number for each jpg file because when we ran adam-01 we chose option “one record per object”

Import records and digital objects (adam-02) In the $alephe_scratch log file it correspondingly states: a file “bradies_numbers” is created which includes the system numbers of the new records 2006-10-26 13:54:07 [log] Number of new doc records : 000000007 2006-10-26 13:54:07 [log] Number of new z403 records: 000000007 2006-10-26 13:54:07 [log] Number of new objects : 000000007 2006-10-26 13:54:07 [log] Number of errors : 000000000

Import records and digital objects (adam-02) Here is system number 50316, for which we changed the information in the bradies.xml template which adam-02 uploaded:

Import records and digital objects (adam-02) Here is system number 50317, for which we did not change the information in the bradies.xml template which adam-02 uploaded: These are the defaults created by adam-01 in the xml template. File name is always given as title.

Import records and digital objects (adam-02) Each record has been given a “view” and “thumbnail” type object: This is because in adam-02 we chose “create thumbnail=Yes”

Import records and digital objects (adam-02) And here it is in the web OPAC: