-
Notifications
You must be signed in to change notification settings - Fork 0
schemasProject_more
Benjamin Riesenberg edited this page Apr 22, 2024
·
7 revisions
🚧🚧🚧
NOTE ⚠
The schemasProject and contentdm_maps repositories must be placed within the same directory in your filesystem
| ...
| schemasProject/
| contentdm_maps/
| ...
- Default guidance (
<instructions>
) and examples (<example>
) allow only theco
attribute, which can be used to state which type of CONTENTdm object(s) the default guidance/example applies to (see details below) - Custom guidance and examples allow up to three attributes,
co
, as well asdd
andgenre_form
; matching on custom guidance prioritizes, in order:
- A match on all three
- A match on
co
anddd
- A match on
dd
- Assign content for describing metadata-creation for a particular type of CONTENTdm object
- Multiple, space-separated values may be assigned
value | description |
---|---|
all | For describing metadata-creation for any kind of CONTENTdm object - standalone item, compound object, or compound-object item |
no | For describing metadata-creation for standalone items |
object | For describing metadata-creation for compound objects |
item | For describing metadata-creation for compound-object items |
agnostic | ⚠ Do not use; not used in current HTML MAP publishing workflow |
See also definition of xs:simpleType name="cdm_object_type_type" in schemasProject/xsd/properties_files.xsd
- Assign content for describing metadata creation for a particular collection
- Multiple, space-separated values may be assigned
- Allowable options are enumerated in schemasProject/xsd/coll_alias.xsd
- The attribute name 'dd' comes from a previous convention of referring to metadata-creation guidance documents as 'data dictionaries'
- Assign content for describing metadata creation for a particular category/genre/form of resource
- Multiple, space-separated values may be assigned
- Allowable options are enumerated in schemasProject/xsd/genre_form.xsd
- Allowable values are the same as for contentdm_maps/xml/ XML MAP files genre_form element
*Retrieve a list of CONTENTdm collection aliases for use in validating attribute values in XML MAP files (see XML MAPs cdmm:xml_map/cdmm:coll_alias) and properties-files (see properties-files //@dd). This data will need to be updated periodically.
- Use
retrieve_collections.py
to create a list of all existing CONTENTdm collection names/collection aliases, output as JSON. - Use
cdm_aliases_to_schema.xsl
to process this JSON data, moving all current collection aliases intocoll_alias.xsd
. - Configure transformation scenario for xsl/cdm_aliases_to_schema.xsl in Oxygen 'Edit scenario' as follows:
- XSLT > XML URL =
../xsd/coll_alias.xsd
- XSLT > XSL URL =
${currentFileURL}
- Output > Save as =
../xsd/coll_alias.xsd
- XSLT > XML URL =
- You may experience validation issues with properties-files content defined by elements in this .xsd file.
- The properties-files elements defined here are not currently used in contentdm_maps transformation code to create metadata guidance documents, but as of writing this legacy data has been retained in properties-files.
View metadata-guidance documents created using this workflow at uwlib-mig.github.io/contentdm_maps