Action needed
(modeling step)
multi
valued
title, predicate: ::RDF::DC.title
rdfs:Literal (string or int)
creator, ::RDF::DC.creator, range: "dc:Agent"
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/elements/1.1/creatorterms/title | Name | None | Required | , if availableYes | 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* | No | Free text | None | Descriptions > Title* | Currently Sufia autofills this with filename. | |||||||||||||||
| X | External ID | 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. Capture Accession # for archival collections. Store the number with a specific prefix based on drop-down choice. Opac link can be displayed by computing on this field. | |||||||||||
| X | Creator | dc11:creator | creator, ::RDF::DC. | publishercreator, range: "dc:Agent" | http://purl.org/dc/elements/1.1/publisher | Descriptions > Publisher | X | Artist | marcrel:art | 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://id.loc.gov/vocabulary/relators/artpurl.org/dc/elements/1.1/creator | |||||||||||
| 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 | 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 | ManufacturerPublisher | marcreldc11:mfr | http://id.loc.gov/vocabulary/relators/mfr | X | Photographer | marcrel:phtpublisher | 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/phtart | ||||||||||||||||||||
| X | (Other) – Removed. This use case is covered by 'creator' and 'contributor' fields. | marcrel:oth | Author | marcrel:aut | http://id.loc.gov/vocabulary/relators/othaut | ||||||||||||||||||
| X | Interviewee | marcrel:ive | http://id.loc.gov/vocabulary/relators/ive | ||||||||||||||||||||
| X | (Depicted)Interviewer | marcrel:dpcivr | http://id.loc.gov/vocabulary/relators/dpcivr | 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? | Subject | dcterms:subject | subject, ::RDF::DC.subject | none, move to skos:Concept | ||||||||||
| X | Manufacturer | marcrel:mfr | http://id.loc.gov/vocabulary/relators/mfr | ||||||||||||||||||||
| X | Photographer | marcrel:pht | http://id.loc.gov/vocabulary/relators/pht | ||||||||||||||||||||
| X | Date of Work | dcterms:date | edm:TimeSpan DC range is rdfs:Literal | http://purl.org/dc/terms/subjectdate | Subject/Topic | RecommendedDate (Range) | Required* | 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 | [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 of Publication | dcterms:issued | rdfs:Literal | http://purl.org/dc/terms/description | issued | Recommended | Yes | [YYYY-MM-DD; YYYY-MM; YYYY; circa YYYY] | 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 | Have Date Published label as a drop-down choice for main Date field. | ||||
| X | Place of Manufacture | marcrel:mfp | based_near covers all this | http://purlid.loc.orggov/dcvocabulary/termsrelators/abstractmfp | 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. X | Inscription? | chf:inscription? | |||||||||||||||||||||
| 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 Interview | marcrel:evp | ditto above | http://id.loc.gov/vocabulary/relators/evp | Yes | Free text with full HTML | |||||||||||||||||
| X | Place of PublicationType | marcreldc11:puptype | basedresource_ | neartype, ::RDF:: | FOAFDC. | based_neartype, range: " | http://xmlns.com/foaf/spec/#term_SpatialThingrdfs:Class" | none | , move to edm:Place?http://idpurl.loc.govorg/vocabularydc/relators/pupelements/1.1/type | Place/Location? | Recommended, if availableType | Required* | Yes | Auto-complete; Label itself is dropDrop-down | optionFAST: Geographics (suggest51); VIAF (alternative option)menu | Selected from DCMI Type | Descriptions > | LocationCurrent Sufia authority service is GeoNames. See VIAF, TGN, FAST, and GeoNames use comparisons on BasecampResource type | Drop-down choices: Moving Image, Still Image, Physical Object, Sound, Text. | ||||
| X | Place of Manufacture | marcrel:mfp | based_near covers all this | Genre | http:// idchemheritage. loc.govorg/ vocabulary/relators/mfpns/hasGenre, moving to edm:hasType | X | Place of Interview | marcrel:evp | ditto above | none, moving to skos:Concept edm:NonInformationResource | http://idwww.loceuropeana.goveu/vocabularyschemas/relatorsedm/evphasType | ||||||||||||
| 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 | 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 | Medium | dcterms:medium chf:medium? (see github notes) | dcterms:PhysicalMedium | http://purl.org/dc/terms/medium | None (maybe for Museum objects later) | Optional | Yes | Auto-complete | AAT | ||||||||||||||
| 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 | Language | dc11:language | language, ::RDF::DC.language, range: "dc:LinguisticSystem" | none | http://purl.org/dc/elements/terms1.1/datelanguage | Date (Range) | Required*Language | Optional | Yes | [YYYY-MM-DD; YYYY-MM; YYYY; circa YYYY] | NoneAuto-complete | TBD | Descriptions > Date Created | Date ranges? Circa? Undated/no date option? Date converters for Gregorian vs. Julian issues? | X | Date Published | dcterms:issuedLanguage | Would it be useful to set default to English? | |||||
| X | Description | dcterms:description | description, ::RDF::DC.description | http://purl.org/dc/terms/issueddescription | None | 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 Maybe? | Free text with full HTML | None | Descriptions > Abstract or Summary | WISYWIG editor possible? Does OH want an Abstract field in addition to Description? | ||||||||||||||||
| new | Inscription | crm:E34_Inscription OR ecrm:E34_Inscription | None | Optional | Yes | Free text with full HTML | None | There are two OWL implementations of the CIDOC CRM vocabulary. I'm not sure if one is better or makes a difference? I think this field could have one larger text box for filling out inscription text, and another single-line text field for inscription location. | |||||||||||||||
X | 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://wwwpurl.europeana.euorg/schemasdc/edmterms/hasTypesubject | Genre | Required*Subject/Topic | Recommended | Yes | DropAuto-down menucomplete | Selected from FAST: Topical, Form/Genre (suggest 50, suggest 55All Facets (suggestall); TGM AAT (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) | 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. | ||||||||||||||||||
| 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* | No | Drop-down menu | Local | Drop-down choices: The Museum at CHF, The Othmer Library of Chemical History, Archives?, Center for Oral History | ||||||||||||||
| new (split from above) | Series Arrangement | bf:materialHierarchicalLevel | rdfs:Literal | http://bibframe.org/vocab/materialHierarchicalLevel | None | Optional, Required for Archival materials | Yes | Free text | None | Free text field for series/intellectual arrangement info. | |||||||||||||
| changed this predicate | Container/Part Number | bf:materialOrganization | rdfs:Literal | http://purlbibframe.org/dcvocab/terms/identifiermaterialOrganization | 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 | ||||||||||||||
| Cat Lu (Unlicensed), let's discuss | Related Materials | dcterms:relation | ?? not sure if this is the same – related_url, ::RDF::RDFS.seeAlso, range: "rdfs:Resource" | pcdm:Object? | http://purl.org/dc/terms/relation | None | Optional | Yes | Auto-complete? | Hydra objects? | |||||||||||||
| dcterms:source is already in use; figure out what it's doing then talk to Cat | OPAC Link (temp name) | dcterms:source | Optional, Required for Archival and serialized materials | No | Four numeric free text fields? | None | Four numerical input fields for Box, Folder, Volume/Issue, and Part numbers. | ||||||||||||||||
| Related URL | Undecided if this field will auto-generate from bib numbers, | ||||||||||||||||||||||
| 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* | DPLA, Europeana + others are working on an international standard for rights statements. Can keep an eye on progress here: https://docs.google.com/document/d/1x10JsIfi8Y74pgJJEAqMtyO5iYp0p6DO5DrOZK-5umY/edit#. Also keeping an eye on this: https://wiki.duraspace.org/display/hydra/Rights+Metadata+Recommendation. Hydra using edm:rights instead of DC. | ||||||||||||
| X | Rights Holder | chemheritage, moving to dcterms:rightsHolder | none, moving to edm:Agent | http://purl.org/dc/terms/sourcerightsHolder | 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" | noneif available | No | TBD | TBD | TBD | |||
| Credit Line | None | Optional | Yes | ||||||||||||||||||||
| X | Provenance | dcterms:provenance | http://purl.org/dc/elements/1.1/languageterms/provenance | LanguageNone | 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? | ||||||||||||||
| X | Rights Holder | dcterms:rightsHolder | edm:Agent | http://purl.org/dc/terms/rightsHolder | None | Required, if available | No | TBD | TBD | TBD | |||||||||||||
| Hold off implementing/Remove? | Keyword/Tags | Keyword/Tags | tag, ::RDF::DC.relationNo | Free text | None | Visible to staff only unless curators want info public? | |||||||||||||||||
| File Creator | |||||||||||||||||||||||
predicate needed | Admin Notes | chf:adminNotes | |||||||||||||||||||||
| Fields we won't implement yet | |||||||||||||||||||||||
| Don't implement this yet | Physical Location | Physical Location | TBD/Topic? | Optional | Yes | Controlled text | Local? | Descriptions > Keyword* | For website taxonomy? Let's hold off on this until we have a better sense of what it could be used for. | ||||||||||||||
| Cat Lu (Unlicensed) what about "Physical container"? Anna Headley (Unlicensed), sounds good. | Physical Container | Container Info | 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? Implement | Access | Access | |||||||||||||||||||||
| Cat Lu (Unlicensed) How is this different from description? Anna Headley (Unlicensed), it was taken from a field where Museums had the exhibition listed. Changing the label so it's clearer. | Related Exhibit | Related Exhibit | |||||||||||||||||||||
| 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. | ||||||||||||||||||||
| 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. | ||||||||||||
| Related Materials | dcterms:relation |
| pcdm:Object? | http://purl.org/dc/terms/relation | None | Optional | Yes | Auto-complete? | Hydra objects? | Thought a bit more about this as curated "related materials," and I think a use case would be when there are multi-volume books that a cataloger wants to relate together. | |||||||||||||
| Unimplement | Abstract (OH?) | dcterms:abstract | http://purl.org/dc/terms/abstract | Optional | No? | Free text with full HTML | I still think Physical Location details would be nice to have in Hydra, but for now manual entry wouldn't get updated effectively. | ||||||||||||||||
| Cat Lu (Unlicensed) what is this for? Anna Headley (Unlicensed), this was meant to be for who created the record, but Hydra captures that already. I want to change this to a Administrative Notes field. | Admin Notes | Admin NotesUnimplement | Table of Contents (OH?) | dcterms:tableOfContents | http://purl.org/dc/terms/tableOfContents | No? | List display? | ||||||||||||||||
| predicate needed | Related Exhibit | Related Exhibit | |||||||||||||||||||||
Here is a list of other things in Sufia. we'll get these for free with default behavior:
- label, ActiveFedora::RDF::Fcrepo::Model.downloadFilename
- part_of, ::RDF::DC.isPartOf
- source, ::RDF::DC.source
- date_uploaded, ::RDF::DC.dateSubmitted
- date_modified, ::RDF::DC.modified
- depositor, ::RDF::URI.new("http://id.loc.gov/vocabulary/relators/dpt")
- arkivo_checksum, ::RDF::URI.new('http://scholarsphere.psu.edu/ns#arkivoChecksum')
- relative_path, ::RDF::URI.new('http://scholarsphere.psu.edu/ns#relativePath')
- import_url, ::RDF::URI.new('http://scholarsphere.psu.edu/ns#importUrl')
- bibliographic_citation, ::RDF::DC.bibliographicCitation
- tag, ::RDF::DC.relation (removed from Sufia from)
- DC.dateCreated (removed from Sufia from)