You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Question, is it possible to create a bag at location A for an existing data directory at B without moving the data into the bag's data/ subdirectory?
My use case is that I want to write a plugin for the monitoring system Checkmk which makes it possible for IT admins to monitor files fo their fixity. To be more concret, let's say a file server shares tons of long-term data which must not change never ever. Bagit would be a perfect fit for a python-based check script which alarms if the integrity of the data is violated.
So I am searching for a way to use Bagit completely non-invasive, because moving the monitored (shared) folder is a no-go.
I am sure that having the payload outside of the bag directory is against the Bagit convention 2.1.2, but is there any workaround I can use to achive my goal?
Thanks,
Simon
PS: I also have seen #67 which is a similar use case.
The text was updated successfully, but these errors were encountered:
Question, is it possible to create a bag at location A for an existing data directory at B without moving the data into the bag's
data/
subdirectory?My use case is that I want to write a plugin for the monitoring system Checkmk which makes it possible for IT admins to monitor files fo their fixity. To be more concret, let's say a file server shares tons of long-term data which must not change never ever. Bagit would be a perfect fit for a python-based check script which alarms if the integrity of the data is violated.
So I am searching for a way to use Bagit completely non-invasive, because moving the monitored (shared) folder is a no-go.
I am sure that having the payload outside of the bag directory is against the Bagit convention 2.1.2, but is there any workaround I can use to achive my goal?
Thanks,
Simon
PS: I also have seen #67 which is a similar use case.
The text was updated successfully, but these errors were encountered: