Currently, Riprap creates events for every resource in a list of resources provided by a fetchresourcelist plugin, looping through the list and creating a fixity check event for each one. It would be useful to be able to create an event on demand for a single resource. One use case for this is to create an initial event immediately after a resource has been ingested into a repository instead of having to wait for the resource to show up in a list provided by a fetchresourcelist plugin. This feature has already been planned in the context the REST interface, via PUT, but it would be desirable to be able to pass a resource Id to the CLI as well (currently, single resources can be checked only by providing the check_fixity command with a resource list containing a single resource).
The process could work as follows. If required data for an event (resource ID, timestamp, outcome, algorithm, and hash value) are present, persist the event. This will be like the "initial fixity events" we already have in that that their outcome isn't the result of comparison against a reference event. These events should have a note indicating they are not based on a reference event, or, where applicable, are the initial event.
If any of the required elements other than resource ID (timestamp, outcome, algorithm, and hash value) are missing from the request, Riprap performs a fixity check event against a reference event. In this case, if no reference event exists, Riprap cannot persist the event.
Currently, Riprap creates events for every resource in a list of resources provided by a fetchresourcelist plugin, looping through the list and creating a fixity check event for each one. It would be useful to be able to create an event on demand for a single resource. One use case for this is to create an initial event immediately after a resource has been ingested into a repository instead of having to wait for the resource to show up in a list provided by a fetchresourcelist plugin. This feature has already been planned in the context the REST interface, via
PUT, but it would be desirable to be able to pass a resource Id to the CLI as well (currently, single resources can be checked only by providing thecheck_fixitycommand with a resource list containing a single resource).The process could work as follows. If required data for an event (resource ID, timestamp, outcome, algorithm, and hash value) are present, persist the event. This will be like the "initial fixity events" we already have in that that their outcome isn't the result of comparison against a reference event. These events should have a note indicating they are not based on a reference event, or, where applicable, are the initial event.
If any of the required elements other than resource ID (timestamp, outcome, algorithm, and hash value) are missing from the request, Riprap performs a fixity check event against a reference event. In this case, if no reference event exists, Riprap cannot persist the event.