Related to #17 - There are other use cases beyond DOI minting where storing the specific metadata from a label (rather than just a Project ID) might be valuable - for example, faceting and filtering based on permitted uses etc.
One thought might bet to:
When viewing an object, evaluate the Project ID and feed it to the API
Pull the metadata from Local Contexts and compare it to what (if any) is stored on the object's Drupal metadata record
If there is a difference, update the Drupal metadata; if no difference, proceed with no changes.
Are there other possible approaches to meet this use case?
Related to #17 - There are other use cases beyond DOI minting where storing the specific metadata from a label (rather than just a Project ID) might be valuable - for example, faceting and filtering based on permitted uses etc.
One thought might bet to:
Are there other possible approaches to meet this use case?