Lot 1 is developing a 'metadata submission tool' for submitting metadata sets to international global data archives in the context of Lot 1 activities. This tool will act by the metadata registry portal (beta prototype currently at https://drs-beta.bopen.eu), or by an installed stand-alone software.
Need to clarify if this is true:
Each Lot 1 metadata record == Lot 2 Data Collection
Can Lot 1 implement automated upload of 'collection_info.yml' and provide a tool to upload data files by its metadata submission tool?
Is this an appropriate/useful pipeline?
They would like to do this, preferably using FTP as the automated upload method.
Primary key ('Unique_metadata_record_ID') used in Lot 1 records should be used in Lot 2 systems as well for provenance and maintainability.
Suggest that the Arrivals Server might not be the best option for synchronising our inventories. It might be easier to have a more direct feed from Lot 1 to Lot 2. Suggest we use Lot1/2 Mtg to discuss.
Lot 1 is developing a 'metadata submission tool' for submitting metadata sets to international global data archives in the context of Lot 1 activities. This tool will act by the metadata registry portal (beta prototype currently at https://drs-beta.bopen.eu), or by an installed stand-alone software.
Need to clarify if this is true:
Can Lot 1 implement automated upload of 'collection_info.yml' and provide a tool to upload data files by its metadata submission tool?
Primary key ('Unique_metadata_record_ID') used in Lot 1 records should be used in Lot 2 systems as well for provenance and maintainability.