This command is geared towards the setup of pipelines for the ETL of metadata from collection registration systems to diverse data sinks and back. In other words: it's geared towards the automatic exchange of object records in MARC, DC, LIDO,... format.
We should check out if the factory is a good tool for data managers to generate IIIF manifest.json objects based on record data.
Flow
Fetch data from a source (OAI, flat file,...)
Apply a fix which generates IIIF manifest.json structure
Push the generated JSON to a data sink.
Of course, we currently focus on generating a set of flat files (ie. 500 records => 500 separate flat files) But nothing prevents us from using a dedicated DAM application which serves the data from a database backend (mongodb??) as a set of manifest.json files.
Currently, we only support one command: transport
This command is geared towards the setup of pipelines for the ETL of metadata from collection registration systems to diverse data sinks and back. In other words: it's geared towards the automatic exchange of object records in MARC, DC, LIDO,... format.
We should check out if the factory is a good tool for data managers to generate IIIF manifest.json objects based on record data.
Flow
Of course, we currently focus on generating a set of flat files (ie. 500 records => 500 separate flat files) But nothing prevents us from using a dedicated DAM application which serves the data from a database backend (mongodb??) as a set of manifest.json files.
Needs to be researched...