When CDEs are imported into CEDAR, they keep their original identifier for reference in the public ID field. However, CEDAR users can create artifacts with arbitrary public IDs, and can duplicate the artifacts they have access to (e.g., CDE fields in the public CDE folder). This can make it difficult to distinguish a user's copy from authorized original content. We need to label 'authentic' artifacts created by organizations or groups of users (e.g., NCI caDSR, NCBI, NLM, or CEDAR administrators).
Solution: Label authentic artifacts with a 'trust seal' to show its validity.
CEDAR will work with such groups to add a "trust seal" to their artifacts, per their own policies.
First case: Imported CDE fields will receive a trust seal from NCI caDSR
Trusted seals:
Get added by CEDAR automatically (e.g., on import) when criteria are met
Are visible in workspace views of artifacts, and in template editor view
Show the organization (e.g., as a pop-up tip) defining the trust policy
Are only available for templating artifacts (fields, elements, templates)
Do not get transferred to copies of the trusted artifact
In future, trusted seals may:
Be enabled manually by trusted individuals in an organization
Apply to other artifacts like folders or metadata instances
Support multiple seals for a single artifact / be visually unique
When CDEs are imported into CEDAR, they keep their original identifier for reference in the public ID field. However, CEDAR users can create artifacts with arbitrary public IDs, and can duplicate the artifacts they have access to (e.g., CDE fields in the public CDE folder). This can make it difficult to distinguish a user's copy from authorized original content. We need to label 'authentic' artifacts created by organizations or groups of users (e.g., NCI caDSR, NCBI, NLM, or CEDAR administrators).
Trusted seals:
In future, trusted seals may:
Additional analysis notes: https://docs.google.com/document/d/1lqPMUxDMybxAA3l-ZhLmnG0Tj3k07Jnvn60FZfXkPno/edit?usp=sharing