Template management analysis #64
Description
We need to find a more efficient way to create and manage templates
- across environments
- across applications
Template managers are a subset of advanced catalogers with experience and knowledge building application profiles using the BIBFRAME ontology. Currently, these are maintained by one cataloger across Sinopia's three environments and Blue Core's single development environment.
In the MVP stage, it will be useful to at the very least analyze how we handle template creation and maintenance so that we can develop a plan for managing templates in a production environment.
Additional details:
- The BIBFRAME Ontology and MARC conversion specs continually evovle
- If templates are RDF resources, we will need both a way to update the template and all of the resources that make use of that template
- Template changes should not break every resource using it, as it does now
- The template manager should be able to update the template in one place, and have it update in other environments automatically
- Template editing requires advanced knowledge of BIBFRAME but also of the Sinopia editor and its architecture. Something easier to use would enable more template managers to help keep them up to date
- The way Sinopia manages templates is not the same way that LC manages their profiles
- LC profiles are now public DCTAP: https://bibframe.org/dancer/