managing publish/load/delete for new and deprecated templates

[briesenberg07]

Seems that unless rt @output_load in sinopia_maps.xml is true, nothing should happen for that RT ID (don't output RDF/XML RT, don't output HTML RT, don't post-process or load). But at this point all RTs in the top level are loaded (and also maybe post-processed, etc.?) regardless of @output_load True/False.

[cspayne]

@briesenberg07
Currently, the two stylesheets in ouput-publish_load (001_01_storage_to_rdfxml.xsl and xsl/004_01_prop_set_to_html.xsl) only process rts where @output_load = true.
All other functions in the script process the rdf/xml generated from storage_to_rdfxml - so these are also only rts where @output_load = true.

The only oversight is when @ouput_load is changed to false, but rdf/xml files from before it was changed exist in sinopia_maps.
The question is: do we want the script to ignore (or even delete) these rdf/xml files if @output_load is now false, or should we provide wiki instructions that these files must be manually deleted if @output_load is changed to false.

(a similar question goes for when rts are deleted from sinopia_maps.xml, as the rdf/xml still remains in sinopia_maps - I think once this is decided, it can likely apply to both cases)

[briesenberg07]

Four possible workflows

Starting work on a new template

• When starting work on a new RT, create new rt element in sinopia_maps.xml
• New RT ID components are added to validation for prop_set format and user elements [1] (don't anticipate needing to add new institution or resource RT ID components)

Publishing/loading a new template

• When the RT is ready to be published and loaded to Sinopia, add @output_load="true" to the rt element in sinopia_maps
• Template is published to repo as HTML, RDF/XML, and JSON-LD, and loaded to a Sinopia environment

Deprecating a template

• Remove @output_load from rt element containing the templates ID components
• Template is removed from repo as HTML, RDF/XML, and JSON-LD, and deleted from the Sinopia environment where it had been loaded [2]

Deprecating a template and eliminating its implementation and guidance information

• Delete rt element from sinopia_maps.xml
• Where an implementation_set or guidance_set child element in a prop_set is used only in that RT, delete implementation_set or guidance_set element (and if no other guidance_set child elements remain delete guidance_set element)
• Where an implementation_set or guidance_set child element in a prop_set is used in that RT as well as other RTs, remove deprecated RT ID components only, leaving other RT ID information and content for matching and output

Notes

[1] At present, validation is set up by:

1. manually editing formats.xsd and resources.xsd - this allows validation of new RTs in sinopia_maps.xml
2. Running 003_rt_ids_to_uwsinopia.xsl to update enumerations for rt_id_type in uwsinopia.xsd - this allows validation for @rt_id in prop_sets (for use in various guidance_set elements)

[2] Is this a tall order? RTs may be loaded in Development, Stage, Production, or all three!!