Embargo for metadata

[6tova]

@MichalMed
I would like to address the call for embargo on (specific) metadata. While this may not apply to CCMM metadata itself, it might be essential for potentially sensitive metadata within extensions—for example, metadata describing methodology. Is there a way to implement this functionality within the metadata model? (Thank you)

[petulica]

To better understand your use case, I need more details about the need. Do you need to set an embargo date, or would you prefer to permanently restrict the metadata? While there is an embargo/restricted access, is there anyone (specific group or individual) who should be able to read such metadata? Should all the embargoed metadata attributes use the same date, or can they vary per attribute?
One more question that might seem stupid, but why is methodology sensitive in your case?

[david-antos]

You made me a bit suspicious mentioning "specific" metadata. Metadata of a record can be handled as a unit regarding access permissions, it can be either public, or have controlled access, or accessible only by the record owner.
On the other hand, it is not possible for individual metadata fields to differ.

In addition to that, kindly note that metadata in the NRP should never contain sensitive data (such as, e.g. parts of medical records). Metadata is kept in a database and indexed by external systems. Truly sensitive data should be kept encrypted at rest, this is not feasible to achieve in a metadata database.

[MichalMed]

anyway, we need some specific usecases, that are relevant, until we get them, there is no way in which we can implement anything