https://qanda.digipres.org/tag/bagit Powered by Question2Answer https://qanda.digipres.org/1136/digital-preservation-server-side Is there any guidance/best practice on server side archiving of a webserver ? I can think of things such as documenting hardware setup/partitions/process running etc in text files, using Bag-It for important directories (/etc/, /usr/local/, /home, software in /src, etc), but this seems slightly haphazard.<br /> <br /> I should say the disk image itself *may* be preserved but I would like to ensure the non-OS parts are preserved in a more accessible form.<br /> <br /> And as always, time is short and the budget is small. I'd like to just do enough that whoever may come along in 10 years time doesn't curse me for not saving the one essential thing they need. https://qanda.digipres.org/1136/digital-preservation-server-side Wed, 07 Feb 2018 11:38:10 +0000 https://qanda.digipres.org/217/is-simple-fixity-information-valuable-to-digital-stewards From #digpres14:<br /> <br /> The BagIt specification includes an oxsum in the transfer materials. &nbsp;This oxsum is the size of the bitstream divided by the number of files. &nbsp;Why is simple fixity information like this included when each file also includes a checksum, a much more precise measure of fixity?<br /> <br /> More generally, why do we care about this low-level fixity information? https://qanda.digipres.org/217/is-simple-fixity-information-valuable-to-digital-stewards Wed, 23 Jul 2014 14:07:37 +0000