16-12-7 GRSF implementation¶
7 December - GRSF Implementations, where we stand, what is missing for the first release (CNR-FORTH- FAO)¶
Meeting Coordinate for joining
https://hangouts.google.com/hangouts/_/idlf3hk7dvez7osfpcfqcpl32ye
Meeting Notes
Topics: Verify the status of the activities of the GRSF development, ensure the release of the first version of the GRSF accessible through the iMarine Data Catalogue.
Participants:
CNR (Pasquale Pagano, Costantino Perciante, Francesco Mangiacrapa)
FORTH (Yannis Marketakis)
FAO (Aureliano Gentile)
Notes
- Description of the activities so far. CNR updated the publishing API with the changes that has been proposed in the previous teleconference. FORTH has updated the client components correspondingly and managed to upload some records (from the original sources). Currently FORTH is updating the client component for handling the catalog ID and URL that are returned when publishing a record.
- The resources should have different UUIDs, even if they are different groups (i.e. FIRMS and RAM). FORTH will guarantee that they are unique (they generate a UUID for a given record URI and source)
- The records coming from the original sources have contents in the fields traceability_flag and status. Since they are redundant it is better to remove them (FORTH)
- After publishing a record, we can update, even adding new fields. However this means that we should have an update functionality in the publishing API. Since we do not expect to have updates for the 1st version of the GRSF registry, it is better to postpone it.
- When VRE admin asks for a record update, an incoming request is sent to the GRSF-services-updater component, which: (a) updates the contents of the GRSF KB, and (b) publishes the updated record in the "public" GRSF Data Catalogue.
- After changing the record status to approved, it is possible to change its status again. One new status that is needed is "archived".
Follow-up actions
- FORTH and CNR continue the development activities for the publishing components
- Next week the production portal will be set-up. After that we can start publishing real contents there
- A new testing environment will be created (by cloning the production environment) where all the development activities take place.
Materials
