-
Notifications
You must be signed in to change notification settings - Fork 3
Template Metadata
michelleif edited this page Dec 12, 2021
·
6 revisions
When you create a template, you have to add some data about the template itself: this is the template metadata. Template metadata consists of:
- Template ID
- Class
- Optional classes
- Template Label
- Author
- Remark
- Date
- Resource attributes
Below are tips on filling in each metadata field.
- Enter a unique ID to identifty the template.
- The Template ID will be displayed on the Resource Templates tab in the Label/ID column, and will be searchable there.
- Template ID is required.
- It needs to be in the form *:* or *:*:* or event *:*:*:* where * is any string, except spaces. So a template name could be
my:template
ormy:new:template
ormy:new:best:template
. Do not use spaces! Unfortunately, Sinopia does not warn you if you use spaces, or if your template ID doesn't conform to the *:* pattern, but if you use a non-conforming Template ID, there will be unexpected and hard-to-diagnose problems (such as not being able to find your template and not being able to successfully nest it in another template). - The Sinopia Profiles Working Group's Best Practices for Profiles document, while written for an earlier version of Sinopia, has additional guidelines for the best way to select a Template ID.
- Enter the URI of the Class of the "thing" that will be cataloged by this template.
- The Class will be displayed on the Resource Templates tab in the Resource URI column, and will be searchable there.
- Class is required.
- Sinopia does enforce that this value has to be a URI.
- You can use any class from any ontology. Actually you can put any URI at all here. Sinopia does not check that it's actually a class from an ontology.
- The Class you put here will end up as the object of this RDF statement when the template is used for cataloging:
<> http://www.w3.org/1999/02/22-rdf-syntax-ns#type <your_class>
where<>
is the URI Sinopia will mint for the "thing" that is cataloged.
- A template can be configured with an optional choice of additional classes, so that at editing time, the user can choose an additional class or classes for the resource.
- Any additional class selected by the user at cataloging time will result in another statement like
<> http://www.w3.org/1999/02/22-rdf-syntax-ns#type <optional_class>
- Enter a label that describes the template.
- The Template Label will be displayed on the Resource Templates tab in the Label/ID column, and will be searchable there.
- Template Label is required.
- Templates are listed in order alphabetically by Label on the Resource Templates tab, and in other locations in Sinopia. To make it easier for catalogers to find PCC-endorsed templates, those template Labels start with an underscore (_) so they will sort first.
- There are no requirements for how to construct the label, but the Sinopia Profiles Working Group's Best Practices for Profiles document, while written for an earlier version of Sinopia, has guidelines for the best way to formulate a Label.
- Enter the name of the person or organization who created the template.
- Author is not required.
- The Author will be displayed on the Resource Templates tab in the Author column, and will be searchable there.
- Enter a free text description of the template and its intended use.
- Remark is not required.
- The Remark will be displayed on the Resource Templates tab in the Guiding statement column, and will be searchable there.
- Enter the date the template was created (or last modified--see Editing an existing template).
- Date is not required.
- Use format yyyy-mm-dd. Sinopia doesn't enforce this format, but it's the only format that will enable the date to be displayed on the Resource Templates tab in the Date column.
- The only available resource attribute is
suppressible
, and this attribute is only relevant for templates that you plan to "nest" inside other templates as nested resources. When asuppressible
template is nested inside another template, Sinopia will not create a blank node for the nested template. Note that a template with thesuppressible
resource attribute must have one and only one property template.
Next: Property Templates: Types of fields and options for each
- Home - How To Get Help
- Sinopia background
- Sinopia environments
- Supported browsers
- Ontology, vocabulary, BIBFRAME optimization
- Latest release / What's next
- Earlier releases
- Demo playlist
- Create an account
- Search
- RDF to MARC conversion
- Diacritics and character sets
- Permissions
- Action icons
- QuickStart in creating a description