A repository may wish to record audit events for external processes, such as:
- Workflow steps that happen before material are ingested into the repository
- External processing, such as verifying checksums, performing format migrations, etc.
- Synchronizing with external preservation repository
These can be added to an external triplestore to facilitate querying and processing with audit events from the repository. These can also be added to the repository to allow preservation of the events.
Adding Events to an External Triplestore
Events that happen outside of the repository can be added directly to an external triplestore. The triples used to describe them should be the same as internal events, except they should have rdf:type audit:ExternalEvent:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
curl -X POST -H "Content-Type: text/turtle" --data-binary @event1.ttl http://localhost:8081/openrdf-sesame/repositories/test/statements |
Adding with SPARQL Update
The SPARQL Update command to insert event triples will be similar to:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
curl -X POST -H "Accept-Encoding: identity" -H "Accept: */*" -H "Content-Type: application/x-www-form-urlencoded" -d update=`cat event2.sparql` http://localhost:8081/openrdf-sesame/repositories/test/statements |
Adding Events to
...
the Repository
External audit events can be added to an LDP Container in as a repository resource. For each object, create an LDP Container that manages the audit event relationship automatically:
...