In the publication side of the API we need to handle that a published artefact may apply to many versions. This means that the same artefact may be part of multiple TEA collections.
This can be handled by having all artefacts in an object store, giving each one a unique ID (hash, UUID) and including the artefact ID in the collection.
The API will need methods to handle publication and retrieval of
oej
commented
3 months ago
In the publication side of the API we need to handle that a published artefact may apply to many versions. This means that the same artefact may be part of multiple TEA collections.
This can be handled by having all artefacts in an object store, giving each one a unique ID (hash, UUID) and including the artefact ID in the collection.
The API will need methods to handle publication and retrieval of
by ID
Which means we need
These IDs needs to be persistent.