I think the tools should include de-bagging functionality to reverse the changes made by bag-in-place.
For example, if I pick one of my data directories and bag it, it works file, can be validated. I could zip it and send it to my colleague. But now my data dir has been altered. Any links and paths and references to those data were altered for me (mainly a “data/” was inserted into the path). And there’s no method to undo the alteration. Of course, I can go in manually and move the contents of data back to the parent and then rmdir data and delete the metadata files, etc. but this is rather awkward. And a lot of trouble when I just wanted to zip up a dir for my colleague.. Plain zip does not alter the original. But BDbagging does.
I think the bagging process ought to be a reversible process in this tool.
I think the tools should include de-bagging functionality to reverse the changes made by bag-in-place.
For example, if I pick one of my data directories and bag it, it works file, can be validated. I could zip it and send it to my colleague. But now my data dir has been altered. Any links and paths and references to those data were altered for me (mainly a “data/” was inserted into the path). And there’s no method to undo the alteration. Of course, I can go in manually and move the contents of data back to the parent and then rmdir data and delete the metadata files, etc. but this is rather awkward. And a lot of trouble when I just wanted to zip up a dir for my colleague.. Plain zip does not alter the original. But BDbagging does.
I think the bagging process ought to be a reversible process in this tool.