Saltar al contenido principal
Servicio de soporte de OCLC

Create CONTENTdm output format

  1. Última actualización
  2. Guardar como PDF
Learn how to create an Output Format record to determine which fields are output to CONTENTdm from OLIB.

►Data Exchange Reference Data> Output Formats

An Output Format record for your digital collection, is used to define the fields that are output to CONTENTdm, and to specify the connection/account details.

OLIB supplies an example output format record – CONTENTdm Catcher (Format No. -26).

 This should be copied for each CONTENTdm collection that you want to synchronise with.

  1. In Data Exchange Reference Data> Output Formats, search for the CONTENTdm record, e.g. %content.
  2. Select it in the hitlist and from Other Actions choose Create Close Copy. The example record always has a negative number:
Output Format Number (Key) Domain Descripción
-26 TITLES  CONTENTdm Catcher
  1. Select the newly copied record and switch to modify:
  2. In the copied output format record, make the following changes:
Campo Descripción
Descripción Edit to reflect the nature of the collection, e.g. Butterfly Images...
Domain Leave set to Titles.
Tipo Leave set to Send to CONTENTdm Catcher Service.
Tipo de medio Select the collection media type you created earlier.
Call Ref. Update the "LibraryExportFormatNo" to be the Format No. of your new Output Format record. E.g. in the above record "-26" needs to be updated to e.g. "34".
  1. Edit the Format Text field to provide the desired OLIB data to CONTENTdm collection field mapping.

Please refer to your CONTENTdm Collection details for the values to use for <field> in the XML.

Note the title number must be included in the identi field:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v6="http://catcherws.cdm.oclc.org/v6.0.0/">
<soapenv:Header/>
<soapenv:Body>
<v6:processCONTENTdm>
<action><-ACTION-></action>
<cdmurl><-CDMURL-></cdmurl>
<username><-OPACUSER-></username>
<password><-OPACPW-></password>
<license><-CMDLICENSE-></license>
<collection>/<-CDMCOLLECTION-></collection>
<metadata>
<metadataList>
<!--1 or more repetitions:-->
<metadata>
<field>identi</field>
<value><TN></value>
</metadata>
<metadata>
<field>type</field>
<value><MTLD></value>
</metadata>#TIPD1NN#
<metadata>
<field>date</field>
<value><TIPD1></value>
</metadata>#/TIPD1NN#
<metadata>
<field>title</field>
<value><TI></value>
</metadata>#AUNN#
<metadata>
<field>contri</field>
<value>#A1#<AS>, <AF>#/A1##AU#; <AS>, <AF>#/AU#</value>
</metadata>#/AUNN##PUNN#
<metadata>
<field>publis</field>
<value>#P1##PPNN#<PP> : #/PPNN#<PU>#TN1NN#; #/TN1NN##/P1#</value>
</metadata>#/PUNN##ABNN#
<metadata>
<field>descri</field>
<value><AB></value>
</metadata>#/ABNN##SUNN#
<metadata>
<field>subjec</field>
<value>#S1#<SU>#/S1##SU#; <SU>#/SU#</value>
</metadata>#/SUNN##XTNN#
<metadata>
<field>relati</field>
<value>#X1#<XT>#/X1##XT#; <XT>#/XT#</value>
</metadata>#/XTNN##TN2NN#
<metadata>
<field>rights</field>
<value><TN2> ; <GLDESC1></value>
</metadata>#/TN2NN##NONN#
<metadata>
<field>audien</field>
<value>#TINTNN#<TINTNN>; #/TINTNN##N1#<NO>#/N1##NO#; <NO>#/NO#</value>
</metadata>#/NONN#
</metadataList>
</metadata>
</v6:processCONTENTdm>
</soapenv:Body>
</soapenv:Envelope>
  1. On the Export Generation sheet in Title Set, select the CONTENTdm Title Set you created earlier.
  2. Specify a Frequency period and a unit from the drop down. (The number of days/weeks/months etc.. between output file (and email) generation). This will be processed during Daystart, so Daily is the most frequently that it will be executed.
  3. Set Enabled to Yes.
  4. Specify a suitable Start On and Output Next On date when the first output file will be generated (and email sent). Specify the same date (e.g. today’s date) in both of these fields. Note: when you initially set up the output format, populate the Output Next On field with the date of the first export, otherwise nothing will export. OLIB will subsequently update it according to the Frequency parameters.
  5. Further down the sheet in FTP / CONTENTdm Details the FTP/CONTENTdm Catcher URL is already completed for you - https://worldcat.org/webservices/contentdm/catcher.
  6. Add the WorldCat User and Password for administering the collection in the FTP/CDM Username and Password fields. This user must have permission to export from and delete from the CONTENTdm collection.
Nota
There are attributes in the User’s Domain for WorldCat Username and Password. If populated, these will be used for the logged in user, for sending new records and edits.
Additionally, if used, these will automatically be passed to the Approval and Indexing pages if clicked. (Experience will vary between browsers).
This allows for the system to permit OLIB users to create Titles and send them to CONTENTdm, but without the privilege to approve records or index the collection, they cannot be made public until someone else logs in to Approve them.
  1. Enter appropriate information in the CONTENTdm License, Server URL and Collection ID fields, for example:

CONTENTdm License: ABCDE-12345-ABCDE-12345
Server URL: server12345.contentdm.oclc.org:8888
CONTENTdm Collection ID: oclcsample

(Do not put a leading “/” in the Collection ID field)

  1. If required for your OLIB implementation, enter appropriate values for the Additional Connectivity Requirements fields - Certificate store, proxy server/port, proxy username/password.

(If not specified, then the values configured for the Link Checker will be utilised. Therefore, if your Link Checker is working as expected, you will very likely not need to specify anything here).

On saving the details this completes the CONTENTdm configuration.

Using Layout Manager, the system manager needs to add the CONTENTdm attributes to your cataloguing layout in order to Synchronise Titles with CONTENTdm.