Action needed (modeling step) | Property | Predicate (formerly Elements) | Sufia property, predicate, range | Range | Predicate URI | search-able? | Facet | Required/ Recommended/ Optional | multi valued | Field Type/Formatting | Authority | Sufia Display location | Notes (asdasdasdasdasdextendingthiscolumnspaceasdasd) |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
X | Title | dcterms:title | title, predicate: ::RDF::DC.title | rdfs:Literal (string or int) | http://purl.org/dc/terms/title | None | Required* | No | Free text | None | Descriptions > Title* | Currently Sufia autofills this with filename. | |
X | Creator | dc11:creator | creator, ::RDF::DC.creator, range: "dc:Agent" note in sufia this is the creator of the file. we are using it more at the work-level | none, move to edm:Agent | http://purl.org/dc/elements/1.1/creator | Name | Required, if available | Yes | Auto-complete; Label itself is drop-down option | FAST: Personal Names, Corporate Names (suggest00, suggest 10); VIAF (alternative option - API info: https://platform.worldcat.org/api-explorer/VIAF); Local data? (see notes) | Allow non-authority names? Discuss NACO workflow. Should we combine Publisher here as well? Is Publisher important enough to warrant a separate facet? | ||
X | Contributor | dc11:contributor | contributor, ::RDF::DC.contributor, range: "dc:Agent" | http://purl.org/dc/elements/1.1/contributor | |||||||||
X | Publisher | dc11:publisher | publisher, ::RDF::DC.publisher, range: "dc:Agent" | http://purl.org/dc/elements/1.1/publisher | Descriptions > Publisher | ||||||||
X | Artist | marcrel:art | http://id.loc.gov/vocabulary/relators/art | ||||||||||
X | Author | marcrel:aut | http://id.loc.gov/vocabulary/relators/aut | ||||||||||
X | Interviewee | marcrel:ive | http://id.loc.gov/vocabulary/relators/ive | ||||||||||
X | Interviewer | marcrel:ivr | http://id.loc.gov/vocabulary/relators/ivr | ||||||||||
X | Manufacturer | marcrel:mfr | http://id.loc.gov/vocabulary/relators/mfr | ||||||||||
X | Photographer | marcrel:pht | http://id.loc.gov/vocabulary/relators/pht | ||||||||||
X | (Depicted) | marcrel:dpc | http://id.loc.gov/vocabulary/relators/dpc | Subject/Topic | Recommended | Yes | (Descriptions > Subject) | Do we want this defined separately, as opposed to keeping this with Subjects? | |||||
Discuss: technically dcterms:subject has no range but there's a skos note that it's intended to be used with a non-literal. make it dc11:subject? Anna Headley (Unlicensed), wont' use with FAST make them non-literals? Cat Lu (Unlicensed), it would if we were going to store the URI, but we're going to start by storing the string. Displaying a label from a URI is not current sufia functionality. this is what the applied linked data interest group is sprinting on right now. Anna Headley (Unlicensed), got it. Let's go with dc11 for now then. | Subject | dc11:subject | subject, ::RDF::DC.subject, range: none but note that it is intended for use with non-literal | none, move to skos:Concept | http://purl.org/dc/terms/subject | Subject/Topic | Recommended | Yes | Auto-complete | FAST: All Facets (suggestall); AAT (possible expansion) | Descriptions > Subject | One search for all or dropdown with authority choices? Check with Anna for best implementation. Temporal and Spatial Coverage ("aboutness") should be cataloged here. | |
X | Description | dcterms:description | description, ::RDF::DC.description | http://purl.org/dc/terms/description | None | Recommended | Maybe? | Free text with full HTML | None | Descriptions > Abstract or Summary | WISYWIG editor possible? Does OH want an Abstract field in addition to Description? | ||
X | Abstract (OH?) | dcterms:abstract | http://purl.org/dc/terms/abstract | Optional | No? | Free text with full HTML | |||||||
X | Table of Contents (OH?) | dcterms:tableOfContents | http://purl.org/dc/terms/tableOfContents | No? | List display? | ||||||||
Cat Lu (Unlicensed), I think it's worth asking hydra-tech if they know of an existing predicate before we create our own. Anna Headley (Unlicensed), that makes sense. I may have also asked this before, but can we repeat predicates for different properties? For example, ideally, this would go under dcterms:description too, but that's already being used for Description. Cat Lu (Unlicensed), no we cannot; (that's why we had to find a different predicate for the genre field) X | Inscription? | chf:inscription? | Yes | Free text with full HTML | |||||||||
X | Place of Publication | marcrel:pup | based_near, ::RDF::FOAF.based_near, range: "http://xmlns.com/foaf/spec/#term_SpatialThing" | none, move to edm:Place? | http://id.loc.gov/vocabulary/relators/pup | Place/Location? | Recommended, if available | Yes | Auto-complete; Label itself is drop-down option | FAST: Geographics (suggest51); VIAF (alternative option) | Descriptions > Location | Current Sufia authority service is GeoNames. See VIAF, TGN, FAST, and GeoNames use comparisons on Basecamp. | |
X | Place of Manufacture | marcrel:mfp | based_near covers all this | http://id.loc.gov/vocabulary/relators/mfp | |||||||||
X | Place of Interview | marcrel:evp | ditto above | http://id.loc.gov/vocabulary/relators/evp | |||||||||
X | Date Created | ebucore:dateCreated (PCDM) | date_created, ::RDF::DC.created | None | No form field | No | Auto-generated | None | File Details > Characterization > ? | Creation date of the scan? Can Hydra capture this in file details? Not sure. This is currently a user-supplied field - sufia's file description says "The date on which the file was generated. Dates are accepted in the form YYYY-MM-DD, e.g. 1776-07-04." @Anna Headley (Unlicensed), looks ebucore has another digization date/time, so I think for our use case this one will be for the creation of the resource/record. Sufia sort of also captures this in Date Uploaded right now, so I'm happy leaving this as a Sufia default (or off altogether). I just don't want it to confuse catalogers, because what we really want them to supply is the date of the original material. Let's discuss more if that was confusing. | |||
X | Date Original | dcterms:date | edm:TimeSpan | http://purl.org/dc/terms/date | Date (Range) | Required* | Yes | [YYYY-MM-DD; YYYY-MM; YYYY; circa YYYY] | None | Descriptions > Date Created | Date ranges? Circa? Undated/no date option? Date converters for Gregorian vs. Julian issues? | ||
X | Date Published | dcterms:issued | http://purl.org/dc/terms/issued | Recommended | Yes | [YYYY-MM-DD; YYYY-MM; YYYY; circa YYYY] | None | Have Date Published label as a drop-down choice for main Date field. | |||||
X | Type | dc11:type | resource_type, ::RDF::DC.type, range: "rdfs:Class" | none | http://purl.org/dc/elements/1.1/type | Type | Required* | Yes | Drop-down menu | Selected from DCMI Type | Descriptions > Resource type | Drop-down choices: Moving Image, Still Image, Physical Object, Sound, Text. | |
X | Genre | http://chemheritage.org/ns/hasGenre, moving to edm:hasType | none, moving to skos:Concept | http://www.europeana.eu/schemas/edm/hasType | Genre | Required* | Yes | Drop-down menu | Selected from FAST: Topical, Form/Genre (suggest 50, suggest 55); TGM (possible expansion for graphic materials); AAT (possible expansion for museum objects) | Drop-down choices (to be finalized with curators): Photographs, Oral histories, Rare books, Manuscripts, Painting, Prints, Scientific apparatus and instruments, Artifacts?, Ephemera? | |||
X | Extent | dcterms:extent | http://purl.org/dc/terms/extent | None | Recommended | Yes | Numeric free text? | None | Variable extent/dimensions across collections. Set standard for measurements. | ||||
X | Medium | dcterms:medium | http://purl.org/dc/terms/medium | None (maybe for Museum objects later) | Optional | Yes | Auto-complete | AAT | Does Museum team want free text for Medium cataloging or controlled terms? | ||||
X | Identifier (Physical Object) | dcterms:identifier | identifier, ::RDF::DC.identifier | rdfs:Literal | http://purl.org/dc/terms/identifier | None | Required* | Yes* | Free text with drop-down | None | Descriptions > Identifier | Re-label Sufia element as External ID. Different drop-down label choices depending on depositor or resource type? Object ID, Bib. #, Item #, OH Interview #, AS Ref. ID. | |
Look at how collections work by default. This is probably in there (see also part_of, in list below - same predicate) | Collection | dcterms:isPartOf | pcdm:Collection? | http://purl.org/dc/terms/isPartOf | Collection | Required, if available | Yes | Auto-complete? | Hydra collections controlled vocabulary? | Collections > Descriptions > Title* | Set reciprocal relationships with HasPart. | ||
dcterms:source is already in use; figure out what it's doing then talk to Cat | Division | chf:division or edm:currentLocation or dcterms:source | pcdm:AdministrativeSet | Division | Required* | Yes | Drop-down menu | Local | Drop-down choices: The Museum at CHF, The Othmer Library of Chemical History, Archives?, Center for Oral History | ||||
dcterms:source is already in use; figure out what it's doing then talk to Cat | OPAC Link (temp name) | dcterms:source | http://purl.org/dc/terms/source | None | Required, if available | No | URI | None | Descriptions > Related URL | Link back to OPAC record for collection information. Can maybe use bib/item numbers if available. | |||
X | Language | dc11:language | language, ::RDF::DC.language, range: "dc:LinguisticSystem" | none | http://purl.org/dc/elements/1.1/language | Language | Optional | Yes | Auto-complete | TBD | Descriptions > Language | ||
X | Rights | dc11:rights | rights, ::RDF::DC.rights, range: "dc:RightsStatement" | http://purl.org/dc/elements/1.1/rights | Rights | Required* | No | Dropdown menu | Creative Commons, etc. | Descriptions > Rights* | TBD | ||
X | Provenance | dcterms:provenance | http://purl.org/dc/terms/provenance | None | Recommended | No | Free text | None | Visible to staff only unless curators want info public? | ||||
Move to our own namespace as a place holder until we get Agents | Rights Holder | chmheritage, moving to dcterms:rightsHolder | none, moving to edm:Agent | http://purl.org/dc/terms/rightsHolder | None | Required, if available | No | TBD | TBD | TBD | |||
Implement | Physical Container | bf:materialHierarchicalLevel | rdfs:Literal | http://bibframe.org/vocab/materialHierarchicalLevel | None | Optional, Required for Archival materials | No | Three numeric free text fields? | None | Fields for Series, Box, and Folder numbers? | |||
Anna Headley (Unlicensed), this is where I want catalogers to be able to set access to public/private. Seems like Sufia already allows for that so it's not necessary in a field? | Access | Access | |||||||||||
predicate needed | Related Exhibit | Related Exhibit | |||||||||||
predicate needed | Admin Notes | Admin Notes | |||||||||||
Fields we won't implement yet | |||||||||||||
Don't implement this yet | Physical Location | Physical Location | I still think Physical Location details would be nice to have in Hydra, but for now manual entry wouldn't get updated effectively. | ||||||||||
Related Materials | dcterms:relation |
| pcdm:Object? | http://purl.org/dc/terms/relation | None | Optional | Yes | Auto-complete? | Hydra objects? | ||||
...