This works well for cases when we have say a Sample or Event root-identifier and the user did not supply a suffix. However, in the case of Expeditions, we want to provide a unique Expedition landing page on GEOME to describe the Expedition itself in addition to Expedition level metadata (similar to the project metadata). This would be handled in biocode-fims-commons in the RecordsResource.java file to create a back-end service for handling this and returning expedition metadata.
This would build off the current records servce.
Currently, expeditions have expedition GUIDs like:
https://n2t.net/ark:/21547/DXy2
These redirect to:
https://geome-db.org/record/ark:/21547/DXy2
Which the application then sees that there is no suffix so it provides Entity level metadata by redirecting back to EZID:
https://ezid.cdlib.org/id/ark:/21547/DXy2
This works well for cases when we have say a Sample or Event root-identifier and the user did not supply a suffix. However, in the case of Expeditions, we want to provide a unique Expedition landing page on GEOME to describe the Expedition itself in addition to Expedition level metadata (similar to the project metadata). This would be handled in biocode-fims-commons in the RecordsResource.java file to create a back-end service for handling this and returning expedition metadata.