Namespaces for Template Entities

[martinjoconnor]

We should have user-centric namespaces for elements, templates, fields. The namespace should contain the organization or user and/or the project. The element names should be unique inside those namespaces.

Currently, all templates, elements and fields are created in the same common namespace or context. The tool should allow users to create entities in different contexts (e.g., based on the user, project, group, etc.), so that users will be able to use the same entity name (e.g., organism, study, principal investigator, etc.) at different levels without name collisions. By using a context, the element ‘org.stanford.bmir.cedar.organization’ would be clearly different from the element ‘org.oxford.isa.organization’.

[martinjoconnor]

Current approach has worked well.

Effectively attaching meaning to entity names is not a good idea.

Explicit provenance can be used to represent this type of information.

e.g.,
metadatacenter/cedar-project#780
metadatacenter/cedar-project#783