-
Notifications
You must be signed in to change notification settings - Fork 36
cr publish.sh
Tim L edited this page May 15, 2015
·
17 revisions
Conversion process phase: publish
- The original need was to step into each conversion cockpit to invoke the extant publication trigger.
- A newer need is to handle custom publication triggers anywhere within the dataset abstraction hierarchy. e.g. https://github.com/tetherless-world/opendap/blob/master/data/source/us/opendap-prov/version/retrieve.sh#L77 for https://github.com/tetherless-world/opendap/wiki/OPeNDAP-Provenance
- The newest need was to publish the given files into htdocs and SPARQL endpoint -- a generalization of aggregate-source-rdf.sh for any file type instead of just RDF (they need to get linked into htdocs).
Predecessors:
- convert-aggregate.sh was the original and is only used in the tabular conversion workflow.
- aggregate-source-rdf.sh assumed just rdf input files.