introduction
Automated exports from an institute local system through a script/workflow. In contrast to the https://health-ri.atlassian.net/wiki/spaces/FSD/pages/edit-v2/292880393?draftShareId=a11733bc-5522-448c-aeae-527390b75106 option, this puts the export logic outside of the source application.
This approach requires the knowledge of a data steward in collaboration with the local IT department.
explanation/approach
The source data is contained within an application within the institute. An automated export will require access to the underlying data, for example through an API or direct database (read) access.
Link to example application: https://github.com/health-ri/img2catalog
pros/cons
Pro
Close to the source material
Con
Requires frequent execution
Next steps
copy/link to https://health-ri.atlassian.net/wiki/spaces/FSD/pages/279183386/3.+Exposing+metadata#%3Acheck_mark%3A--Next-steps