Closed science closed 8 years ago
LR nodes should not accept /publish api for communities that it is not pre-configured to accept.
Propose that we call this field envelope_community
instead of metadata_community
as some people are getting confused about what a metadata community even means. What we're really talking about is a community that is set up to share envelopes. And those envelopes are passed through a special validation process based on the community they are affiliated with..
We need a concept of a
metadata_community
scoping feature in the product. This means that organizations can submit envelopes to a specific community by including that attribute in the envelope.The server, when it receives an envelope directed at a specific community would resolve the community and undertake validation of the envelope and resource based on the community.
Once the envelope & resource are persisted into the DB, the backup to archive.org would also be partitioned by community. So each
metadata_community
would have an archive.org collection that it is configured to back up to. Each community would back up to a distinct archive.org collection.