Initial concept for generalized ID generation in JSON-LD templates
Ids (@id keys) are generated by putting the id itself into the specified template. Should there be some kind of configuration option to it? For now, this is sufficient and will work, but there should be a more intelligent solution to it.
The problem is missing information on the agent part, which can only be supplied manually in our use case: The agent will supply metadata to a CouchDB instance from the another network segment. By doing so, the URI to the CouchDB instance is not equal to the public URI. Right now, this needs to be handled by setting the URI explicitly in the Jinja-templates, but this seems non-optimal.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information