Data Dictionary
The Cornell University Library's Registry of Digital Collections is structured upon three types of entities:
A collection is an aggregation of digital resources, and may include digital images, text documents, sound files, video, metadata, or any combination of these and any other resource types. Collections are often unified by a common subject, location, format, provenance, ownership, etc.
A service provides some form of access to a collection. It may be a human-readable website that can be viewed in a Web browser, or it may be a machine-actionable Web service such as a SRU interface or an OAI repository.
An agent is a person or organization that may own a collection, maintain a service, etc.
The properties for each entity type are described below.
Namespaces
The entity types are based upon the IESR metadata model, although, based on local preferences and needs, existing properties have been modified, and additional properties from the IMLS DCC Collection Description and Dublin Core Collection Description Application Profile have been added. The metadata elements of this Data Dictionary come from the following namespaces:
| Prefix | Name | URI |
|---|---|---|
| cld | Collection Description Terms | http://purl.org/cld/terms/ |
| culcd | Cornell University Library Collection Description | URIs to be determined |
| dc | Dublin Core Metadata Element Set, v1.1 | http://purl.org/dc/elements/1.1/ |
| dcterms | Dublin Core Terms | http://purl.org/dc/terms/ |
| gen | Dublin Core non-collection-specific properties | URIs to be determined |
| iesr | JISC Information Environment Service Registry (IESR) Metadata Terms | http://iesr.ac.uk/terms/# |
| imls | IMLS DCC Collection Description Metadata Schema | http://imlsdcc.grainger.uiuc.edu/registry/imlsdccprofile.xsd |
| rslpcd | RSLP Collection Description | http://purl.org/rslp/terms# |
An XML version of the Data Dictionary is available for download. Last modified: 2007-08-07T16:49:00-04:00
Collection
The Collection entity has the following properties. View summary info as a table.
- Access rights
- Accrual method
- Accrual periodicity
- Accrual policy
- Accumulation date range
- Alternative title
- Associated collection
- Associated publication
- Audience
- Collection identifier
- Collection logo URL
- Contact
- Contents date range
- Controlled vocabularies
- Custodial history
- Delivery platform
- Description of collection
- Geographic coverage
- Item format
- Item type
- Language of collection
- Metadata schema
- Notes about collection
- Physical collection
- Rights
- Rights to use collection items
- Service providing access
- Size of collection
- Sub-collection
- Subject
- Super-collection
- Temporal coverage
- Title of collection
- Type
- Usage statistics
| Access rights | |
| Metadata element | dcterms:accessRights |
|---|---|
| Entity | |
| Definition | A statement of any access restrictions placed on the collection, including allowed users, charges, etc. |
| Data type | Character string |
| Required | no |
| Repeatable | no |
| Help text | Enter a statement of any access restrictions placed on the collection, including allowed users, charges, etc. If there are no restrictions, enter "None". |
| Example | No access restrictions Access is limited to: Full and part time students and employees of Cornell University (including faculty, staff, affiliated researchers and independent contractors) and unaffiliated users who are physically present in Library facilities. |
| Accrual method | |
| Metadata element | dcterms:accrualMethod |
|---|---|
| Entity | |
| Definition | The method by which items are added to the collection. |
| Data type | Character string |
| Encoding scheme | cld:DCCDAccrualMethod |
| Required | no |
| Repeatable | yes |
| Help text | Select the method by which items are added to the collection. |
| Possible values | Deposit | Donation | Purchase | Loan | License | ItemCreation |
| Accrual periodicity | |
| Metadata element | dcterms:accrualPeriodicity |
|---|---|
| Entity | |
| Definition | The frequency with which items are added to the collection. |
| Data type | Character string |
| Encoding scheme | cld:DCCDAccrualPeriodicity |
| Required | no |
| Repeatable | yes |
| Comment | The values of cld:DCCDAccrualPeriodicity come from the MARC Holdings 853$w code specification. Notably lacking is a value to indicate that the collection is closed, no longer adding items. (IMLS includes "No longer adding" in their short list of values.) |
| Help text | Select the frequency with which items are added to the collection. |
| Possible values | Annual | Bimonthly | Semiweekly | Daily | Biweekly | Semiannual | Biennial | Triennial | Three times a week | Three times a month | Continuously updated | Monthly | Quarterly | Semimonthly | Three times a year | Weekly | Completely irregular |
| Accrual policy | |
| Metadata element | dcterms:accrualPolicy |
|---|---|
| Entity | |
| Definition | The policy governing the addition of items to the collection. |
| Data type | Character string URI |
| Required | no |
| Repeatable | yes |
| Help text | Enter the collection development policy governing the addition of items to the collection. When available, include the URL to such the policy. |
| Accumulation date range | |
| Metadata element | dcterms:created |
|---|---|
| Entity | |
| Definition | The range of dates over which the digital collection was accumulated. |
| Data type | Date |
| Encoding scheme | gen:RKMS-ISO8601 |
| Required | no |
| Repeatable | no |
| Help text | Enter the range of dates over which the digital collection was accumulated. Dates should be entered only as specifically as is known. |
| Example | 2003 1998/2001 [1998 through 2001] 1995-01/ [January 1995 to the present] |
| MARC field | 008/07-10 (See MARC 008 documentation), 260c |
| Alternative title | |
| Metadata element | dcterms:alternative |
|---|---|
| Entity | |
| Definition | Any form of name used as a substitute or alternative to the formal name of the collection. |
| Data type | Character string |
| Required | no |
| Repeatable | yes |
| Help text | Enter any alternative form of the collection title, including acronyms or other shortened forms. |
| Example | Political Americana HEARTH |
| MARC field | 246, 740 |
| Associated collection | |
| Metadata element | cld:associatedCollection |
|---|---|
| Entity | |
| Relation to entity | |
| Definition | Another collection that is associated (by provenance) with the current collection. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | yes |
| Help text | If this collection is associatd (by provenance) with another collection, select the associated collection. (An associated collection must be added to the Registry before it appears in the list.) |
| Associated publication | |
| Metadata element | dcterms:isReferencedBy |
|---|---|
| Entity | |
| Definition | A publication that is based on the use, study, or analysis of the collection. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | yes |
| Comment | similar to imls:supplement |
| Help text | If applicable, enter the URI of any publications that are based on the use, study, or analysis of the collection. |
| Audience | |
| Metadata element | dcterms:audience |
|---|---|
| Entity | |
| Definition | Education level of group for whom the collection is intended or useful. |
| Data type | Character string |
| Required | no |
| Repeatable | yes |
| Comment | DO NOT USE |
| Help text | Select the target audience (if any) for the collection. |
| MARC field | 008/22 (See MARC 008 documentation) |
| Collection identifier | |
| Metadata element | dc:identifier |
|---|---|
| Entity | |
| Definition | Any identifier used for the collection. |
| Data type | Character string |
| Qualifier | system = (Ockham|Voyager|ERM) |
| Required | yes |
| Repeatable | yes |
| Comment | Each identifier should be qualified by the system from which the identifier originates. The system (OCKHAM) ID is required, and is automatically generated. The Cornell Voyager bibID is also required. In the future, the bibID could be used to import Voyager data into the registry. A possible additional identifier would be the ERM ID for the license record for the collection, which could also be used to import data into the registry. (The ERM record can be accessed via a URL that responds with an XML record, for example: http://erms.library.cornell.edu/xrecord=l1000030 -- rights info appears near end of record.) |
| Help text | The OCKHAM ID is generated automatically. Enter the Voyager Bib ID for the collection, if available. |
| Example | Cornell:104 [Ockham ID] 5072389 [Voyager ID] |
| MARC field | 001 |
| Collection logo URL | |
| Metadata element | iesr:logo |
|---|---|
| Entity | |
| Definition | A URL for the logo for the collection. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | no |
| Help text | Enter the URL for the graphical logo for the collection. |
| Example | http://campusgw.library.cornell.edu/img/collections/main_moa.jpg |
| Validation notes | Validate the URL by successfully fetching the URL. |
| Contact | |
| Metadata element | dc:contributor |
|---|---|
| Entity | |
| Relation to entity | |
| Definition | A contact person (or organization) responsible for some aspect of a digital collection. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Qualifier | role = (owner|curator|rightsContact|databaseAdministrator|interfaceDesigner) |
| Required | no |
| Repeatable | yes |
| Help text | Select one or more agents, and their role pertaining to the collection. (An agent must be added to the Registry before it appears in the list.) |
| Contents date range | |
| Metadata element | cld:dateContentsCreated |
|---|---|
| Entity | |
| Definition | The range of dates over which the individual items within the collection were created. |
| Data type | Date Range |
| Encoding scheme | gen:RKMS-ISO8601 |
| Required | no |
| Repeatable | yes |
| Comment | A date range should be supplied in the form described by RKMS-ISO8601. Start dates and end dates should be in the form of a date or date-time combination as specified by W3CDTF. Start dates and end dates should be separated by a solidus (forward slash) (/). Either the start date or the end date may be omitted to indicate an open-ended date range. According to several websites, B.C. dates can supposedly be notated using negatives, so that is 1 B.C. is written "0000", 2 B.C. is written "-0001", etc. |
| Help text | Enter the range of dates over which the original items the collection were created. |
| Example | 1888/1894 [date of the original photographs, 1888 through 1894] 1960/ [from 1960 onwards] 2000-02/2003 [from February 2000 through 2003] |
| Controlled vocabularies | |
| Metadata element | iesr:usesControlledList |
|---|---|
| Entity | |
| Definition | A classification scheme or thesaurus used by the collection. |
| Data type | Character string |
| Encoding scheme | iesr:CtrldVocabsList |
| Required | no |
| Repeatable | yes |
| Help text | Select a classification scheme or thesaurus used by the collection. |
| Possible values | LCSH | GEM | AAT | TGN |
| Custodial history | |
| Metadata element | dcterms:provenance |
|---|---|
| Entity | |
| Definition | A statement of any changes in ownership and custody of the collection that are significant for its authenticity, integrity, and interpretation. |
| Data type | Character string |
| Required | no |
| Repeatable | yes |
| Comment | Not in OCKHAM, being added from DC CD AP. |
| Help text | Enter the custodial history; a statement of any changes in ownership and custody of the collection that are significant for its authenticity, integrity, and interpretation. |
| Example | AgCensus was formerly hosted by Oregon State as part of their now-discontinued "GovStats" system. Custody and maintenance of the AgCensus site was transferred to Cornell in January 2004. |
| Delivery platform | |
| Metadata element | culcd:platform |
|---|---|
| Entity | |
| Definition | The name and version of the software used to deliver the collection on the web. |
| Data type | Character string |
| Required | no |
| Repeatable | yes |
| Help text | Enter one or more hardware or software configurations, including version numbers, and a date range for each. |
| Example | Luna Insight 5.1 (2005-08/) Luna Insight 4.0 (2003-04/2005-08) HTML website (2001/2003-04) FileMaker Pro 3.0v4 (1996-2001) |
| Description of collection | |
| Metadata element | dcterms:abstract |
|---|---|
| Entity | |
| Definition | A summary description of the content of the collection. |
| Data type | Character string |
| Required | yes |
| Repeatable | no |
| Help text | Enter a brief, paragraph-length description of the collection (not more than 1000 characters). |
| Example | HEARTH is a core electronic collection of books and journals in Home Economics and related disciplines. Published between 1850 and 1950, these titles were selected by teams of scholars for the great historical importance they hold. The full text of these materials, as well as bibliographies and essays on the wide array of subjects relating to Home Economics, are all freely accessible on this site. |
| MARC field | 520 |
| Validation notes | Check that text is not more than 1000 characters. |
| Geographic coverage | |
| Metadata element | dcterms:spatial |
|---|---|
| Entity | |
| Definition | The spatial coverage of the content of the items in the collection. |
| Data type | Character string |
| Encoding scheme | dcterms:LCSH dcterms:TGN |
| Qualifier | vocab = (none|LCSH|TGN) |
| Required | no |
| Repeatable | yes |
| Help text | Enter a term describing the geographic coverage of the collection content. If the term comes from a controlled vocabulary, indicate the vocabulary used. |
| Example | Iceland Africa, Sub-Saharan |
| MARC field | 651 subfields a and z 6xx subfield z |
| Item format | |
| Metadata element | iesr:itemFormat |
|---|---|
| Entity | |
| Definition | The physical or digital characteristics of the items in the Collection. |
| Data type | Character string |
| Encoding scheme | dcterms:IMT |
| Required | no |
| Repeatable | yes |
| Comment | Note that this is different from dc:format, which would describe the format of the collection itself; iesr:itemFormat describes the format of the items in the collection. |
| Help text | Select the physical or digital characteristics of the items in the Collection. |
| Example | text/plain text/xml image/jpeg image/tiff application/pdf video/quicktime |
| Item type | |
| Metadata element | iesr:itemType |
|---|---|
| Entity | |
| Definition | The nature or genre of the items in the Collection. |
| Data type | Character string |
| Encoding scheme | dcterms:DCMIType |
| Required | no |
| Repeatable | yes |
| Help text | Select one or more types of items found in the collection. |
| Possible values | Collection | Dataset | Event | Image | InteractiveResource | MovingImage | PhysicalObject | Service | Software | Sound | StillImage | Text |
| Language of collection | |
| Metadata element | dc:language |
|---|---|
| Entity | |
| Definition | A language of the content of the items in the collection. |
| Data type | Character string |
| Encoding scheme | dcterms:ISO639-2 |
| Required | no |
| Repeatable | yes |
| Help text | Select the languages found in the collection content. |
| MARC field | 008 (primary language), 041 (may contain other languages, but not necessarily all languages used) |
| Metadata schema | |
| Metadata element | imls:metadataSchema |
|---|---|
| Entity | |
| Definition | The name of the metadata standard(s) used, if any, to describe the items in the digital collection. |
| Data type | Character string |
| Required | no |
| Repeatable | yes |
| Help text | Enter one or more metadata standards used to describe the collection. Include version numbers if available. |
| Example | Dublin Core RFC1807 TEI (SGML) TEI (XML) EAD (SGML) EAD (XML) VRA 2.0 VRA 4.0a DPubS journal DTD (XML) Euclid journal DTD (XML) |
| Notes about collection | |
| Metadata element | imls:notes |
|---|---|
| Entity | |
| Definition | A statement of any additional information about the digital collection. |
| Data type | Character string |
| Required | no |
| Repeatable | yes |
| Help text | Enter any additional information about the collection. |
| Example | Scheduled for public launch in September 2007. |
| MARC field | 5xx |
| Physical collection | |
| Metadata element | dc:source |
|---|---|
| Entity | |
| Definition | The physical collection(s) from which the current digital collection is derived. |
| Data type | Character string |
| Required | no |
| Repeatable | yes |
| Help text | If applicable, enter the name of the physical collection from which this digital collection is derived. |
| Example | Detroit News Photo Archive |
| Rights | |
| Metadata element | dc:rights |
|---|---|
| Entity | |
| Definition | A statement of any rights held in/over over the collection. |
| Data type | Character string |
| Required | no |
| Repeatable | no |
| Help text | Enter a copyright statement for the collection. When available, include a URL pointing to additional rights information. |
| Example | Copyright 2005 by Cornell University. |
| Rights to use collection items | |
| Metadata element | iesr:useRights |
|---|---|
| Entity | |
| Definition | A statement about the allowed usage of data from the collection, for example, terms and conditions. |
| Data type | Character string URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | yes |
| Help text | Enter a statement about the allowed usage of collection items, for example, terms and conditions. |
| Example | Authorized Users may electronically display, download, print, and digitally copy a reasonable portion (generally one or two articles or one book chapter) of the Licensed Materials. |
| Service providing access | |
| Metadata element | iesr:hasService |
|---|---|
| Entity | |
| Relation to entity | |
| Definition | A service that provides access to the collection. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | yes |
| Repeatable | yes |
| Help text | Select one or more services that provide access to this collection. (A service must be added to the Registry before it appears in the list.) |
| Size of collection | |
| Metadata element | dcterms:extent |
|---|---|
| Entity | |
| Definition | The size of the collection in gigabytes (and, optionally, as a count of images or documents). |
| Data type | Character string |
| Qualifier | unit = (gigabytes|images|documents) exact = (exact|approx) |
| Required | no |
| Repeatable | yes |
| Help text | Enter the collection size (in gigabytes), and where appropriate, the number of images or documents in the collection. Additionally, free text can be used to record other units of measure, such as the number of volumes, pages, etc. |
| Example | 8.7 | gigabytes | approx 24000 | images | approx 124 journal titles | -- | -- 6400 journal issues | -- | approx 520000 pages | -- | approx |
| Sub-collection | |
| Metadata element | dcterms:hasPart |
|---|---|
| Entity | |
| Relation to entity | |
| Inverse of | Super-collection |
| Definition | A separately-described collection contained within the current collection. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | yes |
| Help text | If this collection is subdivided into smaller collections, select the sub-collections. (A sub-collection must be added to the Registry before it appears in the list.) |
| Subject | |
| Metadata element | dc:subject |
|---|---|
| Entity | |
| Definition | A topic associated with the items in the collection. |
| Data type | Character string |
| Encoding scheme | dcterms:LCSH |
| Qualifier | vocab = (none|LCSH) |
| Required | yes |
| Repeatable | yes |
| Help text | Enter a term describing the topic of the collection content, indicating whether the term is an LC subject heading. Enter multiple headings/terms separately. |
| Example | Architecture Historic buildings--United States--Periodicals Mathematics -- History |
| MARC field | 6xx |
| Super-collection | |
| Metadata element | dcterms:isPartOf |
|---|---|
| Entity | |
| Relation to entity | |
| Inverse of | Sub-collection |
| Definition | A separately-described collection that contains this collection (i.e., the "parent collection") |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | yes |
| Help text | If this collection is part of a larger collection, select the super-collection. (A sub-collections must be added to the Registry before it appears in the list.) |
| Temporal coverage | |
| Metadata element | dcterms:temporal |
|---|---|
| Entity | |
| Definition | The dates or time periods that are the subject of the collection. |
| Data type | Date Range |
| Encoding scheme | gen:RKMS-ISO8601 |
| Qualifier | vocab = (none|LCSH|dateRange) |
| Required | no |
| Repeatable | yes |
| Help text | If a collection focuses on a particular time period as its subject, enter a date range. Where appropriate, add separate free text terms describing historical periods. |
| Example | 1368/1644 Ming Dynasty |
| MARC field | 648, 6xx subfield y |
| Title of collection | |
| Metadata element | dc:title |
|---|---|
| Entity | |
| Definition | The name of the collection. |
| Data type | Character string |
| Required | yes |
| Repeatable | no |
| Help text | Enter the full title of the collection using "Title Capitalization". Acronyms and other abbreviations should be entered as alternative titles. |
| Example | Cornell University Political Americana Collection Home Economics Archive: Research, Tradition, and History |
| MARC field | 245 |
| Type | |
| Metadata element | dc:type |
|---|---|
| Entity | |
| Definition | The nature or genre of the content of the resource, i.e. dcmitype:Collection. |
| Data type | Character string |
| Encoding scheme | dcterms:DCMIType |
| Required | yes |
| Repeatable | no |
| Comment | According to the 2006-08-24 version of the DC CD AP, this element is now REQUIRED and FIXED (must be dcmitype:Collection). |
| Help text | The value should always be dcmitype:Collection. |
| Possible values | Collection |
| Usage statistics | |
| Metadata element | culcd:statistics |
|---|---|
| Entity | |
| Definition | Information about what type of usage statistics are available for the collection, and how to access these statistics. |
| Data type | Character string URI |
| Required | no |
| Repeatable | no |
| Help text | Describe what type of usage statistics available for the collection, and how they may be accessed. If collection usage statistics are available online, add the URL as a "Service" of the collection. |
Service
The Service entity has the following properties. View summary info as a table.
- Access control
- Access method
- Description of service
- Domain available
- Mediator
- More info about service
- Rights to use service
- Serves collection
- Service administrator
- Service identifier
- Service interface info
- Service language
- Service location
- Service logo URL
- Service name
- Service output type
- Service type
- Standards compliance
| Access control | |
| Metadata element | dcterms:accessRights |
|---|---|
| Entity | |
| Definition | Indication of security of the service. |
| Data type | Character string |
| Encoding scheme | iesr:AuthList |
| Required | yes |
| Repeatable | yes |
| Comment | Note that in IESR, both "Access control" and "Domain available" use the dcterms:accessRights element, and must be distinguished by the xsi:type attribute. |
| Help text | Select the type of security used to control access to the service. |
| Possible values | athens | htpasswd | ip | none | other | password | shibboleth |
| Access method | |
| Metadata element | dc:type |
|---|---|
| Entity | |
| Definition | Technical type of interface providing access to service. |
| Data type | Character string |
| Encoding scheme | iesr:AccMthdList |
| Required | yes |
| Repeatable | no |
| Comment | Note that in IESR, both "Access method" and "Service Type" use the dc:type element, and must be distinguished by the xsi:type attribute. |
| Help text | Select the method of access to the service. |
| Possible values | ftp | ldap | oai-pmh | opengis | opensearch | openurl | rss | rsync | soap | sru | srw | webcgi | webpage | z3950 |
| Description of service | |
| Metadata element | dcterms:abstract |
|---|---|
| Entity | |
| Definition | A free text summary description of the service. |
| Data type | Character string |
| Required | no |
| Repeatable | no |
| Help text | Enter a brief summary description of the service, but only if the description provides further service-related information not contained elsewhere. |
| Domain available | |
| Metadata element | dcterms:accessRights~ |
|---|---|
| Entity | |
| Definition | Information about who can access the service. |
| Data type | Character string |
| Encoding scheme | iesr:DNSDomain |
| Required | no |
| Repeatable | yes |
| Comment | Note that in IESR, both "Access control" and "Domain available" use the dcterms:accessRights element, and must be distinguished by the xsi:type attribute. The tilde at the end of the element name here in the data dictionary should be ignored, but helps to note a second, different usage ofdcterms:accessRights within the Service entity. |
| Help text | If access is restricted by DNS Domain, enter the domain where the service is available. |
| Example | cornell.edu |
| Mediator | |
| Metadata element | iesr:mediator |
|---|---|
| Entity | |
| Definition | A body that mediates access to the service. |
| Data type | URI |
| Encoding scheme | iesr:ShibFed |
| Required | no |
| Repeatable | yes |
| Help text | Enter the URI of a body that mediates access to the service. |
| More info about service | |
| Metadata element | rslpcd:seeAlso |
|---|---|
| Entity | |
| Definition | More information about using the service. |
| Data type | URI |
| Encoding scheme | iesr:SvcHelp iesr:SvcShib iesr:SvcSLA |
| Required | no |
| Repeatable | yes |
| Help text | Enter a URI for any additional information about using the service, such as a help page. |
| Rights to use service | |
| Metadata element | iesr:useRights |
|---|---|
| Entity | |
| Definition | A statement about allowed use of a service, for example terms and conditions. |
| Data type | Character string URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | yes (2 times max) |
| Help text | Enter a statement about the allowed use of the service, such as terms and conditions, or else a URI for such a statement. |
| Serves collection | |
| Metadata element | iesr:serves |
|---|---|
| Entity | |
| Relation to entity | |
| Definition | A collection that the service makes available. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | yes |
| Help text | Select the collection which is made available by this service. |
| Service administrator | |
| Metadata element | rslpcd:administrator |
|---|---|
| Entity | |
| Relation to entity | |
| Definition | An agent that has responsibility for the electronic environment in which the collection is held. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | yes |
| Repeatable | yes |
| Help text | Select an agent that has technical responsibility for the service. |
| Service identifier | |
| Metadata element | dc:identifier |
|---|---|
| Entity | |
| Definition | An identifier of the service. |
| Data type | URI Character string |
| Encoding scheme | dcterms:URI iesr:AthensResource |
| Required | yes |
| Repeatable | yes |
| Help text | An internal OCKHAM ID will be automatically generated for the service. |
| Example | Cornell:34 |
| Service interface info | |
| Metadata element | iesr:interface |
|---|---|
| Entity | |
| Definition | A resource that provides interface information about the service, such as available inputs and outputs, in a machine readable format. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | yes |
| Comment | similar to imls:interactivity |
| Help text | Enter the URI of a resource that provides interface information about the service, such as available inputs and outputs, in a machine readable format. For SOAP services this will be the WSDL/WSIL file. For Z39.50/SRW services it will be the Zeerex file. For Web-cgi services it will be according to an IESR-defined XML schema. |
| Service language | |
| Metadata element | dc:language |
|---|---|
| Entity | |
| Definition | The language of the service. |
| Data type | Character string |
| Encoding scheme | dcterms:RFC3066 |
| Required | no |
| Repeatable | yes |
| Help text | Select the language that a service presents to its users. |
| Service location | |
| Metadata element | rslpcd:locator |
|---|---|
| Entity | |
| Definition | The URI of the access point for the service. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | yes |
| Repeatable | no |
| Help text | Enter the URI of the access point for the service. |
| Example | http://eleusis.library.cornell.edu/ z3950s://zetoc.mimas.ac.uk:2121/zetoc |
| Service logo URL | |
| Metadata element | iesr:logo |
|---|---|
| Entity | |
| Definition | A logo for the service. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | no |
| Help text | Enter a URL for a graphical logo for the service. For an OpenURL Resolver this may be the preferred link button. |
| Service name | |
| Metadata element | dc:title |
|---|---|
| Entity | |
| Definition | Name of the service. |
| Data type | Character string |
| Required | yes |
| Repeatable | no |
| Help text | Enter a descriptive name for the service, reflecting the name of the collection, as well as the type of service. |
| Example | Beyond the Taj website Zetoc Z39.50 search |
| Service output type | |
| Metadata element | iesr:output |
|---|---|
| Entity | |
| Definition | Output format available from the service. |
| Data type | Character string |
| Encoding scheme | dcterms:IMT |
| Required | no |
| Repeatable | yes |
| Help text | Enter the output format available from the service. |
| Example | text/html text/xml application/xhtml+xml |
| Service type | |
| Metadata element | dc:type~ |
|---|---|
| Entity | |
| Definition | Type of the service. |
| Data type | Character string |
| Encoding scheme | iesr:SvcTypeList dcterms:DCMIType |
| Required | no |
| Repeatable | yes |
| Comment | Note that in IESR, both "Access method" and "Service Type" use the dc:type element, and must be distinguished by the xsi:type attribute. The tilde at the end of the element name here in the data dictionary should be ignored, but helps to note a second, different usage of dc:type within the Service entity. |
| Help text | Select the type of the service. |
| Possible values | Alert | Authentication | Authorisation | Institutional Profile Registry | Metadata Schema Registry | OpenURL Resolver | Service Registry | Terminology | User Preferences Registry |
| Standards compliance | |
| Metadata element | iesr:supportsStandard |
|---|---|
| Entity | |
| Definition | Indication of standards and profiles supported by the service. |
| Data type | Character string |
| Encoding scheme | iesr:StdsList |
| Required | no |
| Repeatable | yes |
| Comment | similar to imls:metadataSchema |
| Help text | Select any standards or profiles supported by the service. |
| Possible values | oai-pmh-2_0 | oai-pmh-1_1 | oai-pmh-1_0 | openurl-01 | openurl-1_0 | openurl-sap1 | openurl-sap2 | rss-2_0 | rss-1_0 | rss-0_94 | rss-0_93 | rss-0_92 | rss-0_91 | rss-0_90 | bath-0-a | bath-0-b | bath-0-c | bath-1-a | bath-1-b | bath-1-c | bath-2-a | bath-2-b | bath-2-c | cimi-1 |
Agent
The Agent entity has the following properties. View summary info as a table.
- Address
- Administers service
- Agent URL
- Agent description
- Agent identifier
- Agent logo URL
- Agent name
- Country
- Is contact for collection
- More info about agent
- Phone
- Zip code
| Address | |
| Metadata element | iesr:address |
|---|---|
| Entity | |
| Definition | The postal address of an agent. |
| Data type | Character string |
| Required | no |
| Repeatable | no |
| Help text | Enter the complete physical mailing address of the agent (except for the zip code) |
| Example | 501 Olin Library, Cornell University, Ithaca, NY |
| Administers service | |
| Metadata element | iesr:administers |
|---|---|
| Entity | |
| Relation to entity | |
| Definition | A service that makes a collection available from the electronic environment for which the agent is responsible. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | yes |
| Comment | TODO (20070214) Is this stored as a string (Ockham ID)? |
| Help text | Select a service for which the agent is responsible. |
| Agent URL | |
| Metadata element | dc:relation |
|---|---|
| Entity | |
| Definition | URL for agent. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | no |
| Help text | If the agent has a website, enter the URL. |
| Example | http://www.library.cornell.edu/dlit/dmg.html |
| Agent description | |
| Metadata element | dc:description |
|---|---|
| Entity | |
| Definition | Description of the agent. |
| Data type | Character string |
| Required | no |
| Repeatable | no |
| Comment | The description should not refer to any particular collection or
service. |
| Help text | If the agent is a person, enter the full name in direct order. |
| Example | George Kozak |
| Agent identifier | |
| Metadata element | dc:identifier |
|---|---|
| Entity | |
| Definition | An identifier for Agent. |
| Data type | Character string |
| Required | yes |
| Repeatable | no |
| Help text | An internal Ockham ID will be automatically generated for the agent. |
| Example | Cornell:45 |
| Agent logo URL | |
| Metadata element | iesr:logo |
|---|---|
| Entity | |
| Definition | A logo for agent. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | no |
| Help text | If the agent's organization has a web-accessible logo, enter the URL. |
| Example | http://entomology.library.cornell.edu/100x121bfb3.jpg |
| Agent name | |
| Metadata element | dc:title |
|---|---|
| Entity | |
| Definition | The name of organisation that is the agent. |
| Data type | Character string |
| Required | yes |
| Repeatable | no |
| Comment | The organization name is included here, as required by IESR and recommended
by Ockham. CUL has chosen to use individual persons as agents, for pragmatic internal use. |
| Help text | Enter the name of the agent. If the agent is a person, prefix this field
with the name of the individual's affiliated organization. |
| Example | Cornell University Library (CUL) - George Kozak |
| Country | |
| Metadata element | iesr:country |
|---|---|
| Entity | |
| Definition | The country where an agent is based. |
| Data type | Character string |
| Encoding scheme | dcterms:ISO3166 |
| Required | no |
| Repeatable | no |
| Help text | Select the country where the agent is based. |
| Metadata element | iesr:email |
|---|---|
| Entity | |
| Definition | Email contact address for agent. |
| Data type | Email address |
| Required | yes |
| Repeatable | no |
| Help text | Enter the e-mail address of the agent. For some agents, this may be a listserv or group address. |
| Example | gsk5@cornell.edu mann_gis-l@postoffice.mannlib.cornell.edu |
| Is contact for collection | |
| Metadata element | culcd:isContactFor |
|---|---|
| Entity | |
| Relation to entity | |
| Definition | A collection that the agent legally owns or possesses. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | yes |
| Comment | This property is the inverse of the collection property called "Contact" (dc:contributor). This relationship should be entered from the collection side, so that the role can be specified. TODO (20070214) How is this stored? As a string (Ockham ID)? Must it be entered from the
Collection side? |
| More info about agent | |
| Metadata element | rslpcd:seeAlso |
|---|---|
| Entity | |
| Definition | More information about the agent. |
| Data type | URI |
| Encoding scheme | dcterms:URI |
| Required | no |
| Repeatable | yes |
| Comment | DO NOT USE - use "Agent URL" instead. |
| Help text | Enter a URI for any additional information about the agent. |
| Phone | |
| Metadata element | iesr:phone |
|---|---|
| Entity | |
| Definition | Telephone number of agent. |
| Data type | Telephone number |
| Required | yes |
| Repeatable | no |
| Help text | Enter the international telephone number for the agent. U.S. numbers will begin with '+1' and the area code, and should use '-' as a visual separator. |
| Example | +1-607-255-1949 |
| Zip code | |
| Metadata element | iesr:postcode |
|---|---|
| Entity | |
| Definition | A coded part of the postal address of an agent. |
| Data type | Character string |
| Required | no |
| Repeatable | no |
| Help text | Enter the zip code of the agent's address. |
| Example | 14853 |