We need a way to mark fields as unique across their content type.

When creating content type developers should be able to designate field as unique. Uniqueness should be defined within organization. Because information for a field could be aggregated from multiple data sources we cannot enforce strict uniqueness. However, we can soft enforce it, meaning if an entry already exists we will not allow user to create another one with same unique attribute. But we will not enforce uniqueness on already existing data.

E.g.: User is a member of both cardstack and dotBC organizations. Both have content type tag with name field defined and that field is marked as unique. User should not be permitted to create a tag in cardstack with a names that already exist in it. But if a tag with this name exists in dotBC but not in cardstack user should be allowed to do that.

[dnaidionov]

No, this is something that still needs to be designed. To enable this we would also need some kind of cardstack-SSO solution. The simplest case is that each organization is deployed completely separately. But it’s not exactly clear what happens if 2 “organizations” are deployed on the same hub, or even if that can be done given that we might require complete data separation for whatever reasons - e.g. legal. As Ed mentioned above:

the concept of indices with clear boundaries does not exist and I’m not completely sure we’d want it to. We should plan to discuss in more detail.

So currently we proceed with the assumption that “organization” is deployed on its own instance of hub and doesn’t share its indices with others.

[mansona]

So that second case is the one that I understand and I’m confident I understand the use case 👍

That first one is new to me 🤔 I don’t know the mechanism by which the data in an “organisation” is shared. Do we have an example of this kind of setup yet?