REQUIRED INFORMATION FOR PARTICIPATION IN THE CERL PORTAL
Please complete this form and return it to:
Ivan Boserup
CERL Portal Project Coordinator
Member of the Executive Committee of CERL & Keeper of Manuscripts and Rare Books
The Royal Library
Copenhagen
+45 2020 7744
1. GENERAL INFORMATION
1.1 Display name of database in English
Example: Waller Collection, Uppsala, Sweden
1.2 Short name of database, one word
Example. Waller
1.3 URL to start page or other relevant information page for the database
Example:
1.4 Host country of the database (country code according to ISO 3166,
Example: SE
1.5 Type of contents
Select one
a. Manuscripts
b. Early printed material
1.6 E-mail address of contact person (for internal use only, not displayed in web site)
2. PROTOCOL USED
Select one
a. OAI-PMH (
b. Z39.50 (
3. TECHNICAL SPECIFICATIONS
If 2=a
3.1 The baseURL
3.2 Metadata format to use for mapping to CERL format (must be listed by ListMetadataFormats request, MODS preferred, see 4)
3.3 Set to harvest (if any) (must be listed by ListSets request)
If 2=b
3.4 URL
3.5 Port
3.6 Database name
3.7 Character encoding (UTF-8 preferred)
3.8 Output format (MARC 21 preferred, other formats have to be investigated first)
3.9 User name (if any)
3.10 User group name (if any)
3.11 Password (if any)
4. METADATA MAPPINGS
Please note that no metadata elements are mandatory so all elements do not need to be included.
If 2=a
The metadata records harvested to the CERL Portal are stored in the system in MODS, which is used a common exchange format.
4.1 Name and namespace of metadata root element
Example: oai_dc="
4.2 Other prefixes and namespaces (if any)
Example: dc="
4.3 Full path (except root element) to element(s) with prefix (if other than root) to map to person (name/namePart)
Example: dc:creator
4.4 Full path (except root element) to element(s) with prefix (if other than root) to map to place (originInfo/place/placeTerm)
Example: dc:coverage
4.5 Full path (except root element) to element(s) with prefix (if other than root) to map to title
Example: dc:title (titleInfo/title and subTitle)
4.6 Full path (except root element) to element(s) with prefix (if other than root) to map to subject (subject/topic)
Example: dc:subject
4.7 Full path (except root element) to element(s) with prefix (if other than root) to map to year (originInfo/dateCreated)
Example: dc:date
4.8 Full path (except root element) to element(s) with prefix (if other than root) to map to shelfmark (location/physicalLocation)
Example: dc:identifier
4.9 Full path (except root element) to element(s) with prefix (if other than root) to map to link to original record in source database (identifier)
Example: dc:relation
4.10 Full path (except root element) to element(s) with prefix (if other than root) to map to language (language/languageTerm)
Example: dc:language
4.11 Full path (except root element) to element(s) with prefix (if other than root) to map to general descriptions (abstract)
Example: dc:description
4.12 Full path (except root element) to element(s) with prefix (if other than root) to map to other notes (note)
Example: dc:description
4.13 Full path (except root element) to element(s) with prefix (if other than root) to map to physical description (pshycialDescription/extent and or note)
Example: dc:format
4.14 Hierarchical relations of the type from host to part or vice versa can also be constructed by the relatedItem element in MODS. To build these information must be provided on which element(s) that should create the relation, what the relations is (host/part) and the mapping of other elements within the relation according to the items 4.1-4.13 above.
If 2=b
4.15 Bib-1 Attribute for person
Example: 1
4.16 Bib-1 Attribute for place
Example: 59
4.17 Bib-1 Attribute for title
Example: 4
4.18 Bib-1 Attribute for subject
Example: 21
4.19 Bib-1 Attribute for all words
Example: 1016
4.20 Bib-1 Attribute for year
Example: 30
4.21 Bib-1 Attribute for shelfmark
Example: 53
4.22 Information on how to create a link in the CERL Portal display to the original record in the source database
a. A base URL
Example:
b. A parameter which contains an identifier for the record
Example: BBID
c. An identifier in the retrieved record which can be used as a parameter. Field/subfield must be specified.
Example: field 001