<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Digital Preservation Q&amp;A - Recent questions and answers</title>
<link>https://qanda.digipres.org/qa</link>
<description>Powered by Question2Answer</description>
<item>
<title>Answered: What are current best practices for acquiring &amp; preserving Google Docs?</title>
<link>https://qanda.digipres.org/1148/what-current-best-practices-acquiring-preserving-google-docs?show=1307#a1307</link>
<description>rclone can mass download Google Docs and Spreadsheets and do convert them into Microsoft Office or Libre Office formats on the fly, see &lt;a href=&quot;https://rclone.org/drive/#import-export-of-google-documents&quot; rel=&quot;nofollow&quot;&gt;https://rclone.org/drive/#import-export-of-google-documents&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Of course that will loose the edit history, but you will get a reasonable current snapshot of a document and can perhaps regularly download to track development over time.</description>
<guid isPermaLink="true">https://qanda.digipres.org/1148/what-current-best-practices-acquiring-preserving-google-docs?show=1307#a1307</guid>
<pubDate>Wed, 29 May 2024 14:24:48 +0000</pubDate>
</item>
<item>
<title>Answered: What is a good tool for normalizing image file formats?</title>
<link>https://qanda.digipres.org/1292/what-is-a-good-tool-for-normalizing-image-file-formats?show=1298#a1298</link>
<description>&lt;p&gt;
	Depending on the file format(s) you're dealing with and whether you're comfortable with using command-line tools, ImageMagick might be worth a look:&lt;/p&gt;
&lt;p&gt;
	&lt;a rel=&quot;nofollow&quot; href=&quot;https://imagemagick.org/&quot;&gt;https://imagemagick.org/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	&lt;strong&gt;Don't&lt;/strong&gt; use this if you're using JP2/JPEG2000 though, as the software library ImageMagick is using for this (OpenJPEG) has some serious limitations that might result in losing things like ICC profiles and resolution information. On top of that I think JP2K support has been disabled by default for several years anyway, because of security issues in this library.&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1292/what-is-a-good-tool-for-normalizing-image-file-formats?show=1298#a1298</guid>
<pubDate>Wed, 31 Jan 2024 14:35:22 +0000</pubDate>
</item>
<item>
<title>Answered: What are the most effective ways to minimize latency issues in geographically distributed collections?</title>
<link>https://qanda.digipres.org/294/effective-minimize-geographically-distributed-collections?show=1289#a1289</link>
<description>Latency issues can only be addressed by either improving the connections in between locations or using local caches.&lt;br /&gt;
&lt;br /&gt;
Personally I have found that minio is a good tool if remote data is hosted in object storage. Minio can act as a local object storage proxy that keeps frequently requested data locally available. The tools talking to minio don't get to know if the requested data was locally cached or fetched from remote, but if the cache hits of course it can deliver significantly faster. It can be set up to use a maximum amount of disk space etc.</description>
<guid isPermaLink="true">https://qanda.digipres.org/294/effective-minimize-geographically-distributed-collections?show=1289#a1289</guid>
<pubDate>Fri, 04 Nov 2022 14:22:05 +0000</pubDate>
</item>
<item>
<title>Answered: Does anyone have a procedure in place for redacting selected content (e.g. PII) from files that they can share?</title>
<link>https://qanda.digipres.org/1116/anyone-procedure-place-redacting-selected-content-files-share?show=1288#a1288</link>
<description>&lt;p&gt;
	I was just reminded about this site, and this is a horrendously late answer to this question, but it's a good question and comes up often.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	The advice that stuck with me was from my time at TNA, UK, and the most simple approach is to re-save your file as a simple image format and redact the information with black rectangles in the image editor. You'd then re-save the file without layers, so BMP is a good file format for this. I am reasonably sure JPEG would be just fine as well.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	You could then recreate a PDF in acrobat with the new images if need be.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	The National Archives UK have a redaction toolkit which goes into far more detail and may be of interest to the upvoters of this post.&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
		&lt;a href=&quot;https://cdn.nationalarchives.gov.uk/documents/information-management/redaction_toolkit.pdf&quot; rel=&quot;nofollow&quot;&gt;https://cdn.nationalarchives.gov.uk/documents/information-management/redaction_toolkit.pdf&lt;/a&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1116/anyone-procedure-place-redacting-selected-content-files-share?show=1288#a1288</guid>
<pubDate>Thu, 06 Oct 2022 11:59:41 +0000</pubDate>
</item>
<item>
<title>Answered: How to access a subset of Web Archive pages from a vintage web browser on vintage hardware?</title>
<link>https://qanda.digipres.org/1252/access-subset-archive-pages-vintage-browser-vintage-hardware?show=1287#a1287</link>
<description>&lt;p&gt;
	Get yourself a &lt;a rel=&quot;nofollow&quot; href=&quot;https://pywb.readthedocs.io/en/latest/manual/usage.html#http-s-proxy-mode-access&quot;&gt;pywb proxy&lt;/a&gt; and set it up like this (config.yaml):&lt;/p&gt;
&lt;p&gt;
	&lt;span style=&quot;font-family:courier new,courier,monospace;&quot;&gt;framed_replay: false&lt;br&gt;
	enable_cdx_api: true&lt;br&gt;
	enable_http_proxy: true&lt;br&gt;
	enable_coll_info: false&lt;br&gt;
	proxy:&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp; cookie_resolver: false&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp; coll: proxy&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp; enable_client_rewrite: false&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp; enable_banner: false&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp; default_timestamp: '19980908120000'&lt;br&gt;
	&lt;br&gt;
	collections:&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp; proxy:&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; sequence:&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - index_group:&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ia: memento+&lt;a href=&quot;http://web.archive.org/web/&quot; rel=&quot;nofollow&quot;&gt;http://web.archive.org/web/&lt;/a&gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - index_group:&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; loc: memento+&lt;a href=&quot;http://webarchive.loc.gov/all/&quot; rel=&quot;nofollow&quot;&gt;http://webarchive.loc.gov/all/&lt;/a&gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; uk_na: memento+&lt;a href=&quot;http://webarchive.nationalarchives.gov.uk/&quot; rel=&quot;nofollow&quot;&gt;http://webarchive.nationalarchives.gov.uk/&lt;/a&gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; pt_wa: memento+&lt;a href=&quot;http://arquivo.pt/wayback/&quot; rel=&quot;nofollow&quot;&gt;http://arquivo.pt/wayback/&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;
	Then connect your legacy browser to the service on port 8080 or whatever other port you're running pywb on.&lt;/p&gt;
&lt;p&gt;
	Pywb will act as a proxy to the web archives listed in &quot;sequence&quot; and deliver the un-rewritter, original raw data via memento protocol. The default_timestamp is the time web archives are asked for resources. The first index_group is just the Internet Archive. The second lists the Library of Congress, the UK National Archives, and the Portuguese Web Archive in cas Internet Archive doesn't have a resource. Like this you can build your own oldweb.today so to say, with real hardware.&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1252/access-subset-archive-pages-vintage-browser-vintage-hardware?show=1287#a1287</guid>
<pubDate>Mon, 14 Feb 2022 13:37:00 +0000</pubDate>
</item>
<item>
<title>Answered: What is a good tool to create a graphical map of a web site (sitemap)?</title>
<link>https://qanda.digipres.org/1279/what-is-good-tool-to-create-graphical-map-of-web-site-sitemap?show=1282#a1282</link>
<description>&lt;p&gt;
	This one looks promising and is open source:&lt;/p&gt;
&lt;p&gt;
	&lt;a rel=&quot;nofollow&quot; href=&quot;https://www.astuteo.com/slickmap/&quot;&gt;https://www.astuteo.com/slickmap/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	&lt;a rel=&quot;nofollow&quot; href=&quot;https://github.com/astuteo/slickmap&quot;&gt;https://github.com/astuteo/slickmap&lt;/a&gt;&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1279/what-is-good-tool-to-create-graphical-map-of-web-site-sitemap?show=1282#a1282</guid>
<pubDate>Mon, 22 Nov 2021 03:07:59 +0000</pubDate>
</item>
<item>
<title>Answered: Tools to accession via file transfer</title>
<link>https://qanda.digipres.org/1236/tools-to-accession-via-file-transfer?show=1277#a1277</link>
<description>&lt;p&gt;
	&lt;a rel=&quot;nofollow&quot; href=&quot;https://wormhole.app/&quot;&gt;Wormhole&lt;/a&gt; is great for packages under 10GB (which is twice WeTransfer's limit) since it requires no account and is browser-based.&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1236/tools-to-accession-via-file-transfer?show=1277#a1277</guid>
<pubDate>Fri, 09 Jul 2021 14:48:33 +0000</pubDate>
</item>
<item>
<title>Answered: Best practices for digitising tapes captured at a low resolution</title>
<link>https://qanda.digipres.org/1204/best-practices-for-digitising-tapes-captured-low-resolution?show=1205#a1205</link>
<description>Hi, for VHS do you mean things like long play or EP? What do you mean by low resolution miniDV tapes? I am not aware of a low-res format for DV.&lt;br /&gt;
&lt;br /&gt;
Anyhow, assuming that you mean things like LP and EP for VHS - I would use the same settings as for regular VHS or BetaSP or any tape format where you can't migrate the signal with the same format as the source (like DV) - Uncompressed or Lossless video (I like FFV1 if you want to save some space over uncompressed) using 720x576 for PAL (720x486 for NTSC) with PCM audio.&lt;br /&gt;
&lt;br /&gt;
If a source tape has a weak signal, you should do your very best to capture as much of the data as possible, rather than damaging it even further by using lossy compression or lower resolution.</description>
<guid isPermaLink="true">https://qanda.digipres.org/1204/best-practices-for-digitising-tapes-captured-low-resolution?show=1205#a1205</guid>
<pubDate>Wed, 30 Oct 2019 00:04:23 +0000</pubDate>
</item>
<item>
<title>Answered: Preserving VCD's, what is the best format</title>
<link>https://qanda.digipres.org/1129/preserving-vcds-what-is-the-best-format?show=1186#a1186</link>
<description>&lt;p&gt;
	BIN/CUE seems like an obvious choice for this type of disc. From your question I understand that access is the main issue. If so, I did manage to access BIN/CUE images of Photo CDs (which have a similar layout as VCDs) with CDEmu &lt;a rel=&quot;nofollow&quot; href=&quot;https://cdemu.sourceforge.io&quot;&gt;(https://cdemu.sourceforge.io&lt;/a&gt;). This creates a virtual drive that you can access with any suitable media player (e.g. VLC), just like any ordinary physical drive. If anything this removes any dependency on your media player's to deal with the image format natively.&lt;br&gt;
	&lt;br&gt;
	See also the notes here: &lt;a rel=&quot;nofollow&quot; href=&quot;https://github.com/KBNLresearch/iromlab/issues/93#issuecomment-499073161&quot;&gt;https://github.com/KBNLresearch/iromlab/issues/93#issuecomment-499073161&lt;/a&gt;&lt;br&gt;
	&lt;br&gt;
	Note that I haven't tested this with any actual VCDs because I've been unable to locate any in our collection.&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1129/preserving-vcds-what-is-the-best-format?show=1186#a1186</guid>
<pubDate>Fri, 13 Sep 2019 12:38:16 +0000</pubDate>
</item>
<item>
<title>Answered: External Write Blocker that works with an External Optical Drive?</title>
<link>https://qanda.digipres.org/1140/external-write-blocker-that-works-with-external-optical-drive?show=1183#a1183</link>
<description>The optical media workflows I've come across do not use a write blocker as writing (burning) to optical media is much more difficult to do incidentally than with magnetic or mass storage media. If you absolutely require write blocking for optical media, NYU appear to use write blocked drives according to &lt;a href=&quot;https://archive.nyu.edu/bitstream/2451/43877/2/Schweikert_OpticalMediaPreservationNYU_2018.pdf.&quot; rel=&quot;nofollow&quot;&gt;https://archive.nyu.edu/bitstream/2451/43877/2/Schweikert_OpticalMediaPreservationNYU_2018.pdf.&lt;/a&gt; You can also disable disc burining in the Windows registry &lt;a href=&quot;https://www.technipages.com/enable-disable-cd-burning-windows&quot; rel=&quot;nofollow&quot;&gt;https://www.technipages.com/enable-disable-cd-burning-windows&lt;/a&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1140/external-write-blocker-that-works-with-external-optical-drive?show=1183#a1183</guid>
<pubDate>Thu, 12 Sep 2019 21:40:01 +0000</pubDate>
</item>
<item>
<title>Answered: Is checking fixity at the folder level sufficient for knowing if any files within that folder that been altered?</title>
<link>https://qanda.digipres.org/1141/checking-fixity-sufficient-knowing-within-folder-altered?show=1184#a1184</link>
<description>&lt;p&gt;
	Yes, depending on the method used for computing the checksums and what types of changes you are trying to identify.&amp;nbsp; One solution is to create a tempory archive of the folder and compute the checksum on that file.&amp;nbsp; The following command, using standard GNU/Linux tools will compute a checksum and can be used to identify any change to the files' content, name, persmission, and/or directory structure.&lt;/p&gt;
&lt;pre&gt;
&lt;code&gt;$ tar -cf - somedir | md5sum&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;
	This uses the tar command to create a single archive file for the folder and its contents.&amp;nbsp; The c option creates the archive, the f option specifies a file to save the archive to, the - sets the saved-to file as stdout (temporary), the | character directs the created archive to the next command, md5sum, which computes the checksum.&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	One caveat, this will not indicate which specific files changed (for that a tool like md5deep can be used).&amp;nbsp; Source and additional options/discussion:&amp;nbsp; &lt;a rel=&quot;nofollow&quot; href=&quot;https://unix.stackexchange.com/questions/35832/how-do-i-get-the-md5-sum-of-a-directorys-contents-as-one-sum&quot;&gt;https://unix.stackexchange.com/questions/35832/how-do-i-get-the-md5-sum-of-a-directorys-contents-as-one-sum&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1141/checking-fixity-sufficient-knowing-within-folder-altered?show=1184#a1184</guid>
<pubDate>Thu, 12 Sep 2019 21:39:56 +0000</pubDate>
</item>
<item>
<title>Answered: Best way to read SCSI tape drive on a modern PC?</title>
<link>https://qanda.digipres.org/1160/best-way-to-read-scsi-tape-drive-on-a-modern-pc?show=1185#a1185</link>
<description>I can confirm success using option 1, SCSI to USB adapter, for reading SDLT tapes. &amp;nbsp;&amp;nbsp;&amp;nbsp;Our setup includes HP Storageworks SDLT 320 tape drive, &amp;nbsp;Microtech SCSI-HD50 SCSI Bridge (SCSI to USB adapter), and modern Linux (Ubuntu 18.04 and Bit Curator 14.04 both tested).&lt;br /&gt;
&lt;br /&gt;
With this setup, using mt (to control the tape drive) and tar copy the data has been successful.</description>
<guid isPermaLink="true">https://qanda.digipres.org/1160/best-way-to-read-scsi-tape-drive-on-a-modern-pc?show=1185#a1185</guid>
<pubDate>Thu, 12 Sep 2019 21:39:47 +0000</pubDate>
</item>
<item>
<title>Answered: Does splitting large master files (temporarily) go against best practices?</title>
<link>https://qanda.digipres.org/1135/splitting-large-master-files-temporarily-against-practices?show=1182#a1182</link>
<description>As a temporary process this should not be a concern provided you are able to check the reconstituted files' integrity post reconstitution.&lt;br /&gt;
&lt;br /&gt;
Temporary splitting of files to simplify processing often happens in the background with system copying processes anyway, and all data over the internet is sent as packets then reconstituted into files at the end of the copying process.</description>
<guid isPermaLink="true">https://qanda.digipres.org/1135/splitting-large-master-files-temporarily-against-practices?show=1182#a1182</guid>
<pubDate>Wed, 11 Sep 2019 18:30:31 +0000</pubDate>
</item>
<item>
<title>Answered: Parity data for ISO images: anyone doing this? Best practices?</title>
<link>https://qanda.digipres.org/1117/parity-data-for-iso-images-anyone-doing-this-best-practices?show=1181#a1181</link>
<description>Thought I should try to give an actual answer here and not leave it for more years.&lt;br /&gt;
&lt;br /&gt;
I don't know of anyone in the digital preservation community that is doing this and I suspect Andy's comment speaks to why. So I also don't know of any best practices. &amp;nbsp;It's not the same as saying that absolutely nobody is but it seems likely that nobody is so hopefully answers your question.</description>
<guid isPermaLink="true">https://qanda.digipres.org/1117/parity-data-for-iso-images-anyone-doing-this-best-practices?show=1181#a1181</guid>
<pubDate>Wed, 11 Sep 2019 16:42:49 +0000</pubDate>
</item>
<item>
<title>Answered: Do you have any LTFS Tape Library Recommendations?</title>
<link>https://qanda.digipres.org/1174/do-you-have-any-ltfs-tape-library-recommendations?show=1178#a1178</link>
<description>&lt;p&gt;
	I know it is a bit late, but I came across this and just in case it helps anyone else here is what I know.&lt;br&gt;
	&lt;br&gt;
	Full disclosure, I work for Magnext which sells tape drive libraries and sells their own brand MagStor which I put together and make software for. I will try to be honest though : )&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	Off the top of my head...&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;
&lt;ul style=&quot;color: rgb(51, 51, 51); font-family: Arial, Helvetica, sans-serif; font-size: 13px;&quot;&gt;
	&lt;li style=&quot;line-height: 17px;&quot;&gt;
		If you use tape for backups, do you use LTO?&amp;nbsp; If you use LTO, do you use LTFS or a different standard/format?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
	LTO is the only option. You could use other things, but you would find support in the future difficult.&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;
&lt;ul style=&quot;color: rgb(51, 51, 51); font-family: Arial, Helvetica, sans-serif; font-size: 13px;&quot;&gt;
	&lt;li style=&quot;line-height: 17px;&quot;&gt;
		What kind of tape drive/library set up do you have?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
	&lt;br&gt;
	The setup you need depends on your requirements. If you only have a couple 100 TB of data and you can access it all from one computer, you could get a single SAS drive and have someone manually load and move files to the tapes. This would only require a few tapes and the transfer would take about a day per tape. May I recommend our MagStor SAS drive (shameless plug)&lt;br&gt;
	&lt;br&gt;
	If you need to be able to easily push and pull data from multiple tapes from many different computers, at this point you would need a library connected to your network. Setting this sort of thing up can be difficult without someone experienced in IT or assistance from the people you are buying the hardware from. The most important thing here is that you have a libary that works well. Most of the parts that make up the libraries are actually the same and the only difference is the firmware installed on them. If that was not the case, it would be prohibitively difficult for us to repair them. This also means that there is not much difference between which one you get, but I could ask our technicians which they prefer if you want an expert opinion on that.&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;
&lt;ul style=&quot;color: rgb(51, 51, 51); font-family: Arial, Helvetica, sans-serif; font-size: 13px;&quot;&gt;
	&lt;li style=&quot;line-height: 17px;&quot;&gt;
		What software do you use to manage your hardware?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
	&lt;br&gt;
	LTFS Software recommendations&lt;br&gt;
	MAC: myLTO&lt;br&gt;
	PC: PreRoll Post and XenData6 work station&lt;/p&gt;
&lt;p&gt;
	I don't have as much experience with the software side of things, but I hope that helps some.&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	LTO is the standard when it comes to tape, but as it stands right now the newest version of the tapes, LTO-8 cannot be sold because of a legal battle between Sony and Fuji Film. Once they can be sold again which will hopefully be very soon, LTO-8 is a good choice because it is 12TB for ~$150. (kind of guessing since they cannot be sold right now)&lt;br&gt;
	&lt;br&gt;
	All LTO drives can read up to two generations back and read one generation back. The only drive that breaks this standard is LTO-8 drives which can only read and write one generation back due to a physical change in the tapes.&lt;/p&gt;
&lt;p&gt;
	I myself have not had much experience using LTFS on a PC as apposed to mac, but there is plenty of different software out there to get you up and running on whatever platform you choose, though you will likely have to pay a monthly fee.&lt;br&gt;
	&lt;br&gt;
	&lt;br&gt;
	&lt;br&gt;
	I am sure I have missed a lot so If you have any more questions, feel free to ask and I will do my best to answer. Tape is complicated, but it is also the most economical and longest lasting option. Good luck!&lt;/p&gt;
&lt;p&gt;
	&lt;br&gt;
	&lt;br&gt;
	&lt;br&gt;
	&lt;br&gt;
	&lt;br&gt;
	&lt;br&gt;
	&lt;br&gt;
	&amp;nbsp;&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1174/do-you-have-any-ltfs-tape-library-recommendations?show=1178#a1178</guid>
<pubDate>Thu, 04 Apr 2019 07:52:47 +0000</pubDate>
</item>
<item>
<title>Answered: Is there any best practice/guidance on where to store, in METS, metadata about digitisation/digital creation processes?</title>
<link>https://qanda.digipres.org/1120/practice-guidance-metadata-digitisation-creation-processes?show=1168#a1168</link>
<description>&lt;p&gt;
	It might be a bit late to answer this, but at the National Library of Luxembourg we have been using METS/ALTO for digitization projects for more than 10 years. All the technical metadata about and resulting from the digitization project is stored in MIX schema elements within a techMD section, as shown below:&lt;/p&gt;
&lt;div&gt;
	&amp;lt;amdSec ID=&quot;IMGPARAM00004&quot;&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;lt;techMD ID=&quot;IMGPARAM00004TECHMD&quot;&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mdWrap MIMETYPE=&quot;text/xml&quot; MDTYPE=&quot;NISOIMG&quot;&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;xmlData&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:mix xmlns:mix=&quot;&lt;a href=&quot;http://www.loc.gov/mix/&quot; rel=&quot;nofollow&quot;&gt;http://www.loc.gov/mix/&lt;/a&gt;&quot;&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:BasicImageParameters&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:Format&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:MIMEType&amp;gt;image/tiff&amp;lt;/mix:MIMEType&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ByteOrder&amp;gt;little-endian&amp;lt;/mix:ByteOrder&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:Compression&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:CompressionScheme&amp;gt;1&amp;lt;/mix:CompressionScheme&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:Compression&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:PhotometricInterpretation&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ColorSpace&amp;gt;1&amp;lt;/mix:ColorSpace&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:PhotometricInterpretation&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:Format&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:File&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ImageIdentifier imageIdentifierLocation=&quot;//Dss2/d/docworks/EXPORT/bnl_lw/1900-09-10_01/tif&quot;&amp;gt;1900-09-10_01-00004.tif&amp;lt;/mix:ImageIdentifier&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:FileSize&amp;gt;25003209&amp;lt;/mix:FileSize&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:Orientation&amp;gt;1&amp;lt;/mix:Orientation&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:DisplayOrientation&amp;gt;1&amp;lt;/mix:DisplayOrientation&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:File&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:BasicImageParameters&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ImageCreation&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ...&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ScanningSystemCapture&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ScanningSystemHardware&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ScannerManufacturer&amp;gt;ASSY.SA&amp;lt;/mix:ScannerManufacturer&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ScannerModel&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ScannerModelName&amp;gt;Digitizing line&amp;lt;/mix:ScannerModelName&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ScannerModelNumber&amp;gt;DL 3000&amp;lt;/mix:ScannerModelNumber&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ScannerModelSerialNo&amp;gt;2006 11 25&amp;lt;/mix:ScannerModelSerialNo&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:ScannerModel&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:ScanningSystemHardware&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ScanningSystemSoftware&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ScanningSoftware&amp;gt;LIBFORMAT (c) Pierre-e Gougelet + Page improver&amp;lt;/mix:ScanningSoftware&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ScanningSoftwareVersionNo&amp;gt;1.0.2519.16684&amp;lt;/mix:ScanningSoftwareVersionNo&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:ScanningSystemSoftware&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ScannerCaptureSettings&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:PixelSize&amp;gt;0.0846666&amp;lt;/mix:PixelSize&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:PhysScanResolution&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:XphysScanResolution&amp;gt;300&amp;lt;/mix:XphysScanResolution&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:YphysScanResolution&amp;gt;300&amp;lt;/mix:YphysScanResolution&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:PhysScanResolution&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:ScannerCaptureSettings&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:ScanningSystemCapture&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:ImageCreation&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;mix:ImagingPerformanceAssessment&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;...&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:ImagingPerformanceAssessment&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;...&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mix:mix&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/xmlData&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;/mdWrap&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;nbsp; &amp;lt;/techMD&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp; &amp;lt;/amdSec&amp;gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
	A complete METS/ALTO sample package can be found on our tender information page:&amp;nbsp;&lt;a rel=&quot;nofollow&quot; href=&quot;http://downloads.bnl.lu/tend2018.html&quot;&gt;downloads.bnl.lu/tend2018.html&lt;/a&gt;&lt;/div&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1120/practice-guidance-metadata-digitisation-creation-processes?show=1168#a1168</guid>
<pubDate>Mon, 17 Sep 2018 09:01:09 +0000</pubDate>
</item>
<item>
<title>Answered: Best way to crawl website from localhost with wget, preserving all files in source directory</title>
<link>https://qanda.digipres.org/1166/crawl-website-localhost-preserving-files-source-directory?show=1167#a1167</link>
<description>&lt;p&gt;
	After getting in touch with pywb author Ilya Kreymer about this, Ilya pointed out pywb's behaviour in this case is triggered by the fact that the generate URL list in this case doesn't contain an exact match for the root URL (&lt;code&gt;&lt;a href=&quot;http://www.nl-menu.nl)&quot; rel=&quot;nofollow&quot;&gt;http://www.nl-menu.nl)&lt;/a&gt;&amp;nbsp;&lt;/code&gt; The CD-ROM from which the files were extracted has no index.htm(l) at the domain root level level, which I suppose is quite unusual.&amp;nbsp; This causes pywb to do a prefix query which in this case results in 80k URLs.&lt;/p&gt;
&lt;p&gt;
	Ilya's suggestion was to explicitly add the domain root to the URL list:&lt;/p&gt;
&lt;pre&gt;
&lt;code&gt;echo &quot;&lt;a href=&quot;http://www.nl-menu.nl/&quot; rel=&quot;nofollow&quot;&gt;http://www.nl-menu.nl/&lt;/a&gt;&quot; &amp;gt; urls.txt&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;
	On top of that I found out I also needed to add entries for the roots of the Dutch and English language home pages:&lt;/p&gt;
&lt;pre&gt;
&lt;code&gt;echo &quot;&lt;a href=&quot;http://www.nl-menu.nl/nlmenu.nl/&quot; rel=&quot;nofollow&quot;&gt;http://www.nl-menu.nl/nlmenu.nl/&lt;/a&gt;&quot; &amp;gt;&amp;gt; urls.txt
echo &quot;&lt;a href=&quot;http://www.nl-menu.nl/nlmenu.en/&quot; rel=&quot;nofollow&quot;&gt;http://www.nl-menu.nl/nlmenu.en/&lt;/a&gt;&quot; &amp;gt;&amp;gt; urls.txt&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;
	Then we can add the remaining files (and rewrite file paths as URLs)&lt;/p&gt;
&lt;pre&gt;
&lt;code&gt;&lt;code&gt;find /var/www/www.nl-menu.nl -type f \
    | sed -e 's/\/var\/www\//http:\/\//g' &amp;gt; urls.txt&lt;/code&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;
	Finally run wget:&lt;/p&gt;
&lt;pre&gt;
&lt;code&gt;wget --page-requisites \
    --warc-file=&quot;nl-menu&quot; \
    --warc-cdx \
    --output-file=&quot;nl-menu.log&quot; \
    --input-file=urls.txt&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;
	This results in a WARC that is both complete &lt;em&gt;and&lt;/em&gt; renders in pywb!&lt;/p&gt;
&lt;h3&gt;
	&amp;nbsp;&lt;/h3&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1166/crawl-website-localhost-preserving-files-source-directory?show=1167#a1167</guid>
<pubDate>Tue, 10 Jul 2018 16:19:03 +0000</pubDate>
</item>
<item>
<title>Answered: Merging &amp; Deduping WARC files</title>
<link>https://qanda.digipres.org/1155/merging-%26-deduping-warc-files?show=1159#a1159</link>
<description>&lt;p&gt;
	for merging, &lt;a href=&quot;https://github.com/chfoo/warcat&quot; rel=&quot;nofollow&quot;&gt;warccat&lt;/a&gt; concat does the job.&lt;/p&gt;
&lt;p&gt;
	for cleaning/dedup: using &lt;a href=&quot;https://sbforge.org/display/JWAT/JWAT-Tools&quot; rel=&quot;nofollow&quot;&gt;JWAT-Tools&lt;/a&gt; you can unpack a warc file&lt;/p&gt;
&lt;p&gt;
	&lt;span style=&quot;font-family:courier new,courier,monospace;&quot;&gt;jwattools.sh unpack your-archive.warc.gz&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;
	the result are single files containing a warc record. then you can remove duplicates or unwanted things and reconstruct the warc just with cat&lt;/p&gt;
&lt;pre class=&quot;moz-quote-pre&quot;&gt;
&lt;span style=&quot;font-family:courier new,courier,monospace;&quot;&gt;cat your-archive.warc.{1,6,10} &amp;gt;your-new-new.warc&lt;/span&gt;&lt;/pre&gt;
&lt;p&gt;
	update: &lt;a href=&quot;https://github.com/tari/warcdedupe&quot; rel=&quot;nofollow&quot;&gt;https://github.com/tari/warcdedupe&lt;/a&gt;&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1155/merging-%26-deduping-warc-files?show=1159#a1159</guid>
<pubDate>Fri, 08 Jun 2018 11:17:22 +0000</pubDate>
</item>
<item>
<title>Answered: Digital Preservation - Server Side</title>
<link>https://qanda.digipres.org/1136/digital-preservation-server-side?show=1158#a1158</link>
<description>&lt;p&gt;
	Sometime ago I migrated a physical server machine to emulated hardware. I added some documentation of the process on an &lt;a href=&quot;http://openpreservation.org/blog/2012/04/23/migrating-windows-2000-database-server-virtualized-and-emulated-hardware/&quot; rel=&quot;nofollow&quot;&gt;OPF blog post here&lt;/a&gt;. With &lt;a href=&quot;http://eaas.uni-freiburg.de&quot; rel=&quot;nofollow&quot;&gt;Emulation as a Service (EaaS) &lt;/a&gt;now very useable you may want to consider following a similar approach. The research team at the University of Freiburg behind EaaS have also been pursing improved features for preserving acess to linked servers and front-ends using the same backend emulation infrastructure and may have some additional ideas that could help with your use case.&amp;nbsp;&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1136/digital-preservation-server-side?show=1158#a1158</guid>
<pubDate>Tue, 01 May 2018 13:33:03 +0000</pubDate>
</item>
<item>
<title>Answered: How/where to store metadata about optical media sector layout in METS/PREMIS</title>
<link>https://qanda.digipres.org/1146/where-store-metadata-about-optical-media-sector-layout-premis?show=1153#a1153</link>
<description>&lt;p&gt;
	So here's a little update:in the end I serialized the cd-info output to XML, and embedded that in a METS techMD/mdWrap element. Here's an example for an 'enhanced' CD with 2 sessions that contain 20 audio tracks and 1 data track, respectively:&lt;/p&gt;
&lt;p&gt;
	&lt;span style=&quot;font-family:courier new,courier,monospace;&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;mets:techMD ID=&quot;techMD_22&quot;&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;mets:mdWrap MIMETYPE=&quot;text/xml&quot; MDTYPE=&quot;OTHER&quot; OTHERMDTYPE=&quot;cd-info output&quot;&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;mets:xmlData&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:cd-info&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:trackList&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:track&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:trackNumber&amp;gt;1&amp;lt;/cd-info:trackNumber&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:MSF&amp;gt;00:02:00&amp;lt;/cd-info:MSF&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:LSN&amp;gt;000000&amp;lt;/cd-info:LSN&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:type&amp;gt;audio&amp;lt;/cd-info:type&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/cd-info:track&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:track&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:trackNumber&amp;gt;2&amp;lt;/cd-info:trackNumber&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:MSF&amp;gt;01:22:02&amp;lt;/cd-info:MSF&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:LSN&amp;gt;006002&amp;lt;/cd-info:LSN&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:type&amp;gt;audio&amp;lt;/cd-info:type&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/cd-info:track&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ::&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ::&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:track&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:trackNumber&amp;gt;20&amp;lt;/cd-info:trackNumber&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:MSF&amp;gt;55:23:38&amp;lt;/cd-info:MSF&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:LSN&amp;gt;249113&amp;lt;/cd-info:LSN&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:type&amp;gt;audio&amp;lt;/cd-info:type&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/cd-info:track&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:track&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:trackNumber&amp;gt;21&amp;lt;/cd-info:trackNumber&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:MSF&amp;gt;59:41:40&amp;lt;/cd-info:MSF&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:LSN&amp;gt;268465&amp;lt;/cd-info:LSN&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:type&amp;gt;data&amp;lt;/cd-info:type&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/cd-info:track&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:track&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:trackNumber&amp;gt;170&amp;lt;/cd-info:trackNumber&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:MSF&amp;gt;63:08:25&amp;lt;/cd-info:MSF&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:LSN&amp;gt;283975&amp;lt;/cd-info:LSN&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:type&amp;gt;leadout&amp;lt;/cd-info:type&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/cd-info:track&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/cd-info:trackList&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:analysisReport&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:cdExtra&amp;gt;True&amp;lt;/cd-info:cdExtra&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:multiSession&amp;gt;True&amp;lt;/cd-info:multiSession&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:mixedMode&amp;gt;False&amp;lt;/cd-info:mixedMode&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;cd-info:fullReport&amp;gt;No CD-TEXT on Disc.&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CD-Plus/Extra&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; session #2 starts at track 21, LSN: 268465, ISO 9660 blocks: 283825&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ISO 9660: 283825 blocks, label `ELL2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; '&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/cd-info:fullReport&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/cd-info:analysisReport&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/cd-info:cd-info&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/mets:xmlData&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/mets:mdWrap&amp;gt;&lt;br&gt;
	&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/mets:techMD&amp;gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;
	A full example METS file (which also includes EbuCore audio metadata, DFXML metadata and Isolyzer output) can be found here:&lt;/p&gt;
&lt;p&gt;
	&lt;a rel=&quot;nofollow&quot; href=&quot;https://gist.githubusercontent.com/bitsgalore/ef164e953ca52218930a4bc512bfe96c/raw/c225a00ef997c99f1898d1f80783f334d357d5c9/mets-cdinfo-dfxml.xml&quot;&gt;https://gist.githubusercontent.com/bitsgalore/ef164e953ca52218930a4bc512bfe96c/raw/c225a00ef997c99f1898d1f80783f334d357d5c9/mets-cdinfo-dfxml.xml&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	Thanks again to Euan and Bertrand for your suggestions!&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1146/where-store-metadata-about-optical-media-sector-layout-premis?show=1153#a1153</guid>
<pubDate>Thu, 08 Feb 2018 17:33:19 +0000</pubDate>
</item>
<item>
<title>Answered: I am looking for a straightforward accession tool. Can people please advise?</title>
<link>https://qanda.digipres.org/1102/looking-straightforward-accession-tool-people-please-advise?show=1103#a1103</link>
<description>I would recommend Data Accessioner. It provides a nice GUI for the FITS toolset, creates and validates chechsums while moving content from external media, and provides a PREMIS XML file output (with flexible output available through subbing in different XSLT files) - &lt;a href=&quot;http://www.dataaccessioner.org/&quot; rel=&quot;nofollow&quot;&gt;http://www.dataaccessioner.org/&lt;/a&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1102/looking-straightforward-accession-tool-people-please-advise?show=1103#a1103</guid>
<pubDate>Wed, 07 Feb 2018 11:38:45 +0000</pubDate>
</item>
<item>
<title>What are the risks involved in a DIY solution like RODA?</title>
<link>https://qanda.digipres.org/1134/what-are-the-risks-involved-in-a-diy-solution-like-roda</link>
<description>I am curious to hear from anyone, particularly smaller institutions, that have implemented DIY solutions with Archivematica, RODA, etc. We have a non-trivial amount of data (300TB - 400TB) that would be cost prohibitive in vendor-based pure cloud scenario using S3 and Glacier.&lt;br /&gt;
&lt;br /&gt;
It seems to me the most cost effective method is to have data on-site in duplicate and replicated to Amazon Glacier, perhaps using a commercial system for the added support. However, its seems (in my ambitious mind) possible to manage a system like RODA in-house and handle the replication ourselves, needing only to pull from Glacier if the fixity checking reports an error. Can someone disabuse me of my fanciful notions? Any horror stories or success stories? Am I right to assume that as long as the bags are stored in Glacier we could migrate those to another system later on if we found maintaining our own system too unwieldy? How horrifying is it to all of you to rely on Glacier as a fail safe option?</description>
<guid isPermaLink="true">https://qanda.digipres.org/1134/what-are-the-risks-involved-in-a-diy-solution-like-roda</guid>
<pubDate>Wed, 07 Feb 2018 11:38:21 +0000</pubDate>
</item>
<item>
<title>Answered: IP limiting/restrictions for providing in-house access to copyrighted/restricted material?</title>
<link>https://qanda.digipres.org/1142/limiting-restrictions-providing-copyrighted-restricted?show=1144#a1144</link>
<description>We do this at NYPL.&lt;br /&gt;
&lt;br /&gt;
Here's an example of something with IP restrictions.&lt;br /&gt;
&lt;a href=&quot;https://digitalcollections.nypl.org/items/66f1db18-ac47-4160-8b3f-c3e8a595815f&quot; rel=&quot;nofollow&quot;&gt;https://digitalcollections.nypl.org/items/66f1db18-ac47-4160-8b3f-c3e8a595815f&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
...and something public on the web&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;https://digitalcollections.nypl.org/items/c90cfcb0-f875-0130-a5d6-3c075448cc4b&quot; rel=&quot;nofollow&quot;&gt;https://digitalcollections.nypl.org/items/c90cfcb0-f875-0130-a5d6-3c075448cc4b&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
...and something IP-restricted linked out of a finding aid&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://archives.nypl.org/scl/22026#c1279014&quot; rel=&quot;nofollow&quot;&gt;http://archives.nypl.org/scl/22026#c1279014&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
IP restrictions are limited by collection to the building that houses the collection. One of the big questions that we still have is making access available more generally outside of a collection's building. That's requiring high-level administration involvment.</description>
<guid isPermaLink="true">https://qanda.digipres.org/1142/limiting-restrictions-providing-copyrighted-restricted?show=1144#a1144</guid>
<pubDate>Wed, 13 Sep 2017 01:22:02 +0000</pubDate>
</item>
<item>
<title>Answered: Managing Timestamps</title>
<link>https://qanda.digipres.org/1088/managing-timestamps?show=1139#a1139</link>
<description>&lt;p&gt;
	We use checksums to prove bit-level preservation; the NDSA report&amp;nbsp;&lt;em&gt;Checking Your Digital Content: What is Fixity, and When Should I be Checking It?&lt;/em&gt;&amp;nbsp;has been a very useful guide to help our institution establish and improve our fixity-checking for preservation and authenticity.&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1088/managing-timestamps?show=1139#a1139</guid>
<pubDate>Mon, 22 May 2017 14:52:49 +0000</pubDate>
</item>
<item>
<title>Answered: Ingesting large &amp; hybrid digital collections</title>
<link>https://qanda.digipres.org/1137/ingesting-large-%26-hybrid-digital-collections?show=1138#a1138</link>
<description>&lt;p&gt;
	My institution has&amp;nbsp;&lt;em&gt;some&lt;/em&gt; experience with larger, heterogeneous collections, though our local practice is still evolving as we add larger and more complex collections to our holdings. &amp;nbsp;I only have one link I can send your way as an example -- a collection of digital files relating to a redistricting project:&amp;nbsp;&lt;a href=&quot;http://www2.mnhs.org/library/findaids/gr00558.xml.&quot; rel=&quot;nofollow&quot;&gt;http://www2.mnhs.org/library/findaids/gr00558.xml.&lt;/a&gt; &amp;nbsp;This finding aid dates back to 2012 and is already a bit outdated for what we plan to do with new/incoming collections, but I think it gives you the general idea.&lt;/p&gt;
&lt;p&gt;
	As you can see from that example, we (generally) rely heavily on original order, and use our descriptive tools (generally EAD finding aids) to try and aid researchers in finding what they're looking for. &amp;nbsp;When there are dependencies between multiple digital objects, we keep them all together in a single .zip download rather than separate them out. &amp;nbsp;The level of description varies in our collections; we previously described every file (as in the above example), but with newer and more homogeneous collections (such as large collections of digital photographs) we tend to describe them at the series level.&lt;/p&gt;
&lt;p&gt;
	I hope that provides some help!&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1137/ingesting-large-%26-hybrid-digital-collections?show=1138#a1138</guid>
<pubDate>Mon, 22 May 2017 14:45:34 +0000</pubDate>
</item>
<item>
<title>Answered: Incomplete ISO image after imaging CD-ROM - how to prevent and detect this?</title>
<link>https://qanda.digipres.org/1076/incomplete-image-after-imaging-rom-prevent-and-detect-this?show=1131#a1131</link>
<description>&lt;p&gt;
	And here's another update; following some additional research I did into this I wrote a blog post:&lt;/p&gt;
&lt;p&gt;
	&lt;a rel=&quot;nofollow&quot; href=&quot;http://openpreservation.org/blog/2017/01/13/detecting-broken-iso-images-introducing-isolyzer/&quot;&gt;Detecting broken ISO images: introducing Isolyzer&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	This also discusses the detection script which I linked to earlier; this has been given a major overhaul and now works for hybrid ISO 9660 / Apple images as well. See:&lt;/p&gt;
&lt;p&gt;
	&lt;a rel=&quot;nofollow&quot; href=&quot;https://github.com/KBNLresearch/verifyISOSize&quot;&gt;https://github.com/KBNLresearch/verifyISOSize&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1076/incomplete-image-after-imaging-rom-prevent-and-detect-this?show=1131#a1131</guid>
<pubDate>Mon, 16 Jan 2017 13:12:25 +0000</pubDate>
</item>
<item>
<title>Answered: Documenting Scope and Content for Web Archives</title>
<link>https://qanda.digipres.org/297/documenting-scope-and-content-for-web-archives?show=1128#a1128</link>
<description>Not sure this is quite what you are after, but we did some work documenting the scope and content of one of our collections here: &lt;a href=&quot;http://data.webarchive.org.uk/opendata/ukwa.ds.2/#issues&quot; rel=&quot;nofollow&quot;&gt;http://data.webarchive.org.uk/opendata/ukwa.ds.2/#issues&lt;/a&gt; and here: &lt;a href=&quot;http://data.webarchive.org.uk/opendata/ukwa.ds.2/host-linkage/#issues&quot; rel=&quot;nofollow&quot;&gt;http://data.webarchive.org.uk/opendata/ukwa.ds.2/host-linkage/#issues&lt;/a&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/297/documenting-scope-and-content-for-web-archives?show=1128#a1128</guid>
<pubDate>Wed, 21 Dec 2016 16:43:16 +0000</pubDate>
</item>
<item>
<title>Answered: Are there accepted alternatives to WAVE for storing audio files larger than 4GB?</title>
<link>https://qanda.digipres.org/1123/there-accepted-alternatives-storing-audio-files-larger-than?show=1127#a1127</link>
<description>We have preserved a few &amp;gt; 4GB WAVE files, we make sure they conform to the RF64 standard. PRONOM was updated recenlty with identification of RF64 WAVE files.</description>
<guid isPermaLink="true">https://qanda.digipres.org/1123/there-accepted-alternatives-storing-audio-files-larger-than?show=1127#a1127</guid>
<pubDate>Wed, 17 Aug 2016 15:57:20 +0000</pubDate>
</item>
<item>
<title>Answered: How can I set up a test instance of Archivematica on OS X (10.11.2)?</title>
<link>https://qanda.digipres.org/1100/how-can-i-set-up-a-test-instance-of-archivematica-on-os-x-10-11-2?show=1105#a1105</link>
<description>Here are instructions for installing Archivematica using Vagrant, for development or testing purposes:&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;https://wiki.archivematica.org/Getting_started#Ansible_.26_Vagrant&quot; rel=&quot;nofollow&quot;&gt;https://wiki.archivematica.org/Getting_started#Ansible_.26_Vagrant&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
If you have trouble, feel free to jump into the Archivematica Technical group: &lt;a href=&quot;https://groups.google.com/forum/#!forum/archivematica-tech&quot; rel=&quot;nofollow&quot;&gt;https://groups.google.com/forum/#!forum/archivematica-tech&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Cheers!</description>
<guid isPermaLink="true">https://qanda.digipres.org/1100/how-can-i-set-up-a-test-instance-of-archivematica-on-os-x-10-11-2?show=1105#a1105</guid>
<pubDate>Fri, 24 Jun 2016 14:29:35 +0000</pubDate>
</item>
<item>
<title>Answered: Best SIP / AIP creation practices for optical carriers that span multiple volumes</title>
<link>https://qanda.digipres.org/1121/creation-practices-optical-carriers-that-multiple-volumes?show=1122#a1122</link>
<description>In our audio digitization projects, it's common to have a single intellectual object span multiple pieces of media; for example, a symphony recorded across the front and backs of a vinyl record. Each face of the record is captured to its own preservation master file. In addition, we create an edit master from each preservation master for accessibility reasons.&lt;br /&gt;
&lt;br /&gt;
In pseudo-JSON it looks like this.&lt;br /&gt;
&lt;br /&gt;
symphony1:{&lt;br /&gt;
&amp;nbsp;record1: {&lt;br /&gt;
&amp;nbsp;&amp;nbsp;face1:{record1_face1_pm.wav, record1_face1_em.wav},&lt;br /&gt;
&amp;nbsp;&amp;nbsp;face2:{record1_face2_pm.wav, record1_face2_em.wav}&lt;br /&gt;
&amp;nbsp;},&lt;br /&gt;
&amp;nbsp;record2: {&lt;br /&gt;
&amp;nbsp;&amp;nbsp;face1:{record2_face1_pm.wav, record2_face1_em.wav},&lt;br /&gt;
&amp;nbsp;&amp;nbsp;face2:{record2_face2_pm.wav, record2_face2_em.wav}&lt;br /&gt;
&amp;nbsp;}&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
In our digitization workflows we ask for the files from each piece of media to be stored in its own bag. In the example, we would receive 2 bags (record1 and record2) that we treat as SIPs. Our repository is Fedora based, so each file set (preservation master, edit master, other derivatives) is stored as one Fedora object, and larger intellectual objects are aggregated through additional Fedora objects. I'm still mapping how this structure fits the OAIS AIP and AIC concepts.</description>
<guid isPermaLink="true">https://qanda.digipres.org/1121/creation-practices-optical-carriers-that-multiple-volumes?show=1122#a1122</guid>
<pubDate>Wed, 22 Jun 2016 18:29:18 +0000</pubDate>
</item>
<item>
<title>Answered: Is there a GUI alternative to Bagger that performs a similar function?</title>
<link>https://qanda.digipres.org/822/there-gui-alternative-bagger-that-performs-similar-function?show=1115#a1115</link>
<description>Adding another relevant tool for anyone who happens on to this question: &lt;br /&gt;
&lt;br /&gt;
Exactly: &lt;a href=&quot;https://www.avpreserve.com/tools/exactly/&quot; rel=&quot;nofollow&quot;&gt;https://www.avpreserve.com/tools/exactly/&lt;/a&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/822/there-gui-alternative-bagger-that-performs-similar-function?show=1115#a1115</guid>
<pubDate>Tue, 03 May 2016 16:22:26 +0000</pubDate>
</item>
<item>
<title>Answered: DIY digitisation, good or bad?</title>
<link>https://qanda.digipres.org/1101/diy-digitisation-good-or-bad?show=1107#a1107</link>
<description>As long as the imaging device you use is capable of creating the quality of scans you want, I don't see how changing the device you use to create the scan would be a problem. &amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
There are some things to check and to consider in order to make sure that happens, of course. &amp;nbsp;I would personally double-check that the optical resolution of the cheaper desktop scanners (not the interpolated resolution) is sufficient to meet your resolution requirements, and that the camera set-up will give you the kinds of images you're looking for (e.g., resolution, lighting, camera stand, etc.). &amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The bigger concern (in my opinion) is all of the administrative questions that need to be answered: Are you able to organize and preserve these new outputs in a way that is consistent with (or part of) your existing procedures? &amp;nbsp;How will you decide what bypasses the existing procedures? &amp;nbsp;Who will be responsible for this new scanning? &amp;nbsp;What are the cost implications? &amp;nbsp;How will you provide access to the files? &amp;nbsp;Would it be better to improve the current workflow instead of adding a new one?&lt;br /&gt;
&lt;br /&gt;
Hope that helps!</description>
<guid isPermaLink="true">https://qanda.digipres.org/1101/diy-digitisation-good-or-bad?show=1107#a1107</guid>
<pubDate>Tue, 05 Apr 2016 13:41:22 +0000</pubDate>
</item>
<item>
<title>Answered: Setting a custom date for wget or wpull?</title>
<link>https://qanda.digipres.org/1097/setting-a-custom-date-for-wget-or-wpull?show=1099#a1099</link>
<description>&lt;p&gt;
	A useful analog may be &lt;a rel=&quot;nofollow&quot; href=&quot;http://library.stanford.edu/blogs/digital-library-blog/2014/10/web-halloween-secrets-resurrecting-slac-dead-website-computer&quot;&gt;our work on the SLAC web archive&lt;/a&gt;. In that case, we web-published then re-captured historical web content with wget into WARC, then adulterated the CDX indices to reflect the &quot;true&quot; timestamps corresponding to the dates of the backups from which we restored the web content. That way, we had both a faithful record of the actual HTTP communications in the WARCs and timestamp-appropriate indexing for the purposes of access.&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1097/setting-a-custom-date-for-wget-or-wpull?show=1099#a1099</guid>
<pubDate>Thu, 17 Dec 2015 18:40:14 +0000</pubDate>
</item>
<item>
<title>Answered: Strategy for preserving scanned files outside of repository</title>
<link>https://qanda.digipres.org/1001/strategy-for-preserving-scanned-files-outside-repository?show=1096#a1096</link>
<description>Here's our final solution: putting the files into Bagger/BagIt bags, then storing in our Research Data Store.&lt;br /&gt;
&lt;br /&gt;
We also set up a mechanism to verify all the checksums on a 2-monthly basis, and added (non-public) links to the bags from our catalogue and research repository.&lt;br /&gt;
&lt;br /&gt;
Thanks, everyone, for your help :-)</description>
<guid isPermaLink="true">https://qanda.digipres.org/1001/strategy-for-preserving-scanned-files-outside-repository?show=1096#a1096</guid>
<pubDate>Sun, 06 Dec 2015 20:26:56 +0000</pubDate>
</item>
<item>
<title>Answered: How should an organisation QA the results of its outsourced web archiving activities?</title>
<link>https://qanda.digipres.org/1089/should-organisation-results-outsourced-archiving-activities?show=1091#a1091</link>
<description>&lt;div&gt;
	Great question! For the Parliamentary Archives, we have done exactly as you describe in terms of outsourcing the majority of our web archive capability to the Internet Memory Foundation. The justification for doing so is simple; we simply wouldn’t have the resources or infrastructure to do so in-house. The Houses of Parliament web estate forms a vital corporate record of the organisations activity which should be preserved and made accessible.&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
	To set our Quality Assurance practices into context, it will help to give a very brief introduction to our web archive process:&lt;/div&gt;
&lt;ol&gt;
	&lt;li&gt;
		First, Archive staff sign-off the Seed List (usually around 30 URL’s).Second, IMF carries out the crawls. There is the option for Archives staff to set off crawls using ArchiveTheNet (AtN).&lt;/li&gt;
	&lt;li&gt;
		An initial QA stage is then done by IMF to identify and rectify initial issues (such as ensuring crawl parameters have been met, technical limitations noted etc.).&lt;/li&gt;
	&lt;li&gt;
		Using project management software (JIRA) IMF then hand over the captured URL’s for the second QA stage which is carried out by Archive staff. We assign one person to lead the QA and then distribute QA tasks across multiple staff.&lt;/li&gt;
	&lt;li&gt;
		Any further QA issues are reported through JIRA and resolved by IMF.&lt;/li&gt;
	&lt;li&gt;
		Finally, captured crawls are delivered by IMF to the Archives for ingest into the Parliament’s digital repository (Preservica Enterprise Edition).&lt;/li&gt;
&lt;/ol&gt;
&lt;div&gt;
	As you can see, there are multiple levels of QA which occur. From the initial QA carried out by IMF, to the second QA undertaken by the Archives. I would argue that there is a final level of QA involved during the ingest workflow as the ARCs/(W)ARC’s are characterised, validated, and virus scanned etc. Setting aside the ingest workflow, the bulk of our QA is a manual human process which involves a significant amount of time checking the captured data. We also have a Service Level Agreement (SLA) with IMF which is vital in ensuring that the required service and QA approaches are met. For obvious reasons, I can’t go into too much detail in terms of what the SLA contains!&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
	I am aware that our process could be improved, and that our QA steps rely upon manual intervention. I’d be happy to discuss in more detail the QA steps I have outlined and potential areas of improvement. I’d also be particularly interested to hear from other web archive experts with suggestions as to what we should be doing as part of our QA activities.&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
	The Parliamentary Archives pages for the web archive can be found here: &lt;a href=&quot;http://www.parliament.uk/business/publications/parliamentary-archives/web-archive/&quot; rel=&quot;nofollow&quot;&gt;http://www.parliament.uk/business/publications/parliamentary-archives/web-archive/&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
	The actual web archive portal (hosted by IMF) is here: &lt;a href=&quot;http://webarchive.parliament.uk/&quot; rel=&quot;nofollow&quot;&gt;http://webarchive.parliament.uk/&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;
	&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
	~Chris Fryer, Senior Digital Archivist, Parliamentary Archives&lt;/div&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1089/should-organisation-results-outsourced-archiving-activities?show=1091#a1091</guid>
<pubDate>Wed, 25 Nov 2015 19:45:43 +0000</pubDate>
</item>
<item>
<title>Answered: Best method to record track playing order for ripped audio CDs</title>
<link>https://qanda.digipres.org/1082/best-method-record-track-playing-order-for-ripped-audio-cds?show=1086#a1086</link>
<description>&lt;p&gt;
	At home, I like using &lt;a rel=&quot;nofollow&quot; href=&quot;http://http://www.exactaudiocopy.de/en/&quot;&gt;Exact Audio Copy.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	It can build a cue sheet which not only keeps the track playing order of a CD intact, but also does something about the gaps between tracks. For some people who do this kind of thing, the ideal would be to rip a segued CD like &quot;Dark Side of the Moon&quot; which exists as separate tracks, but plays back gapless. The cue sheet is apparently able to do this.&lt;/p&gt;
&lt;p&gt;
	However, &lt;a rel=&quot;nofollow&quot; href=&quot;http://kodi.wiki/view/Cue_sheets&quot;&gt;cue sheets&lt;/a&gt; are not supported everywhere, so probably useless for you and not so good for digital preservation. But thought I would mention it.&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1082/best-method-record-track-playing-order-for-ripped-audio-cds?show=1086#a1086</guid>
<pubDate>Tue, 20 Oct 2015 18:52:58 +0000</pubDate>
</item>
<item>
<title>CD-ROM / DVD imaging: is it customary to save scans of booklets / covers as well?</title>
<link>https://qanda.digipres.org/1079/rom-dvd-imaging-customary-save-scans-booklets-covers-as-well</link>
<description>&lt;p&gt;
	I'm&amp;nbsp; trying to compile a minimum set of metadata that an end-user would need for using ISO images from a ~15,000 CD-ROM /DVD collection. In particular I'm wondering about CD booklets and covers. They often contain lots of useful info and documentation related to technical environments and usage instructions. However, having to digitize them would add a substantial overhead on top of the actual imaging workflow. An other option might be to make scans of the actual CDs, which often contain useful info as well. This is what e.g. Internet Archive seems to be doing:&lt;/p&gt;
&lt;p&gt;
	&lt;a href=&quot;https://archive.org/details/SharewearBreakthroughUtil_ProdCol&quot; rel=&quot;nofollow&quot;&gt;https://archive.org/details/SharewearBreakthroughUtil_ProdCol&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	I'm curious how other institutions are dealing with this?&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1079/rom-dvd-imaging-customary-save-scans-booklets-covers-as-well</guid>
<pubDate>Tue, 22 Sep 2015 12:48:07 +0000</pubDate>
</item>
<item>
<title>What organizations are preserving software?</title>
<link>https://qanda.digipres.org/1068/what-organizations-are-preserving-software</link>
<description>&lt;p&gt;
	I've been building a list of organizations that are attempting to preserve software including:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
		NIST's &lt;a href=&quot;http://www.nsrl.nist.gov/&quot; rel=&quot;nofollow&quot;&gt;software reference library&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;
		some game archives such as &lt;a href=&quot;http://blogs.loc.gov/digitalpreservation/2013/02/video-game-preservation-at-scale-an-interview-with-henry-lowood/&quot; rel=&quot;nofollow&quot;&gt;Stanford's&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;
		&lt;a href=&quot;http://www.windowscentral.com/step-inside-microsoft-archives-and-see-past-your-favorite-company&quot; rel=&quot;nofollow&quot;&gt;Microsoft has an internal Archive&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;
		the Internet Archive is doing &lt;a href=&quot;https://archive.org/details/software&quot; rel=&quot;nofollow&quot;&gt;amazing work&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;
		so is the &lt;a href=&quot;http://www.abc.net.au/news/2015-06-20/collecting-retro-computer-technology-to-save-digital-treasures/6560494&quot; rel=&quot;nofollow&quot;&gt;National Library of Australia&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;
		the &lt;a href=&quot;http://playitagainproject.org/&quot; rel=&quot;nofollow&quot;&gt;play it again project&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;
		the &lt;a href=&quot;http://umich.edu/~archive/&quot; rel=&quot;nofollow&quot;&gt;University of Michigan Archive&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;
		Rhizome are preserving &lt;a href=&quot;http://rhizome.org/editorial/2015/apr/17/theresa-duncan-cd-roms-are-now-playable-online/&quot; rel=&quot;nofollow&quot;&gt;software based/dependent art&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;
		as is &lt;a href=&quot;http://www.moma.org/explore/inside_out/2015/05/13/open-sourcing-momas-digital-vault/&quot; rel=&quot;nofollow&quot;&gt;MoMA&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;
		and of course the &lt;a href=&quot;http://www.computerhistory.org/groups/spg/&quot; rel=&quot;nofollow&quot;&gt;computer history museum &lt;/a&gt;is also&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
	There are resources &lt;a rel=&quot;nofollow&quot; href=&quot;http://www.software.ac.uk/resources&quot;&gt;here &lt;/a&gt;and &lt;a rel=&quot;nofollow&quot; href=&quot;http://blogs.loc.gov/digitalpreservation/2012/11/preserving-exe-a-short-list-of-readings-on-software-preservation/&quot;&gt;here &lt;/a&gt;with more information but I'm interested in community input.&lt;/p&gt;
&lt;p&gt;
	But who else is doing software preservation?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	Would anyone else find such a list useful?&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1068/what-organizations-are-preserving-software</guid>
<pubDate>Thu, 13 Aug 2015 20:04:13 +0000</pubDate>
</item>
<item>
<title>Is it problematic to include spaces in file names?</title>
<link>https://qanda.digipres.org/1053/is-it-problematic-to-include-spaces-in-file-names</link>
<description>&lt;p&gt;
	I have read about and heard different opinions about including spaces in file names, and based on casual observation it seems like, as a community, we typically recommend that people do not use spaces in their file names (perhaps for many of the reasons outlined &lt;a rel=&quot;nofollow&quot; href=&quot;http://superuser.com/questions/29111/what-technical-reasons-exist-for-not-using-space-characters-in-file-names&quot;&gt;here&lt;/a&gt;). Do you have experience with working with spaces in file names that provides insight into whether they are problematic? Should we continue to recommend that digital object creators avoid spaces in file names, or is it an obsolete concern?&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1053/is-it-problematic-to-include-spaces-in-file-names</guid>
<pubDate>Thu, 09 Jul 2015 15:53:37 +0000</pubDate>
</item>
<item>
<title>Favorite online resources to learn more about DP tools?</title>
<link>https://qanda.digipres.org/1037/favorite-online-resources-to-learn-more-about-dp-tools</link>
<description>I'm trying to gather information about some ways for folks just starting out in digital preservation to learn more about tools and resources. Any one have favorites, or know of good webinars that can offer more insight on tools? Any information sessions (preferably free) that you'd like to share that you found helpful?&lt;br /&gt;
&lt;br /&gt;
I'm aware of the resources through NDSA and DPOE, and often refer to the COPTR tool grid. But I'd love to see if anyone has other favorites or has a resource they found particularly helpful. For example, the new ArchivesDirect service hosts information sessions and can be a good place for people to learn more about the new hosted service.&lt;br /&gt;
&lt;br /&gt;
Thanks!</description>
<guid isPermaLink="true">https://qanda.digipres.org/1037/favorite-online-resources-to-learn-more-about-dp-tools</guid>
<pubDate>Tue, 07 Jul 2015 20:13:52 +0000</pubDate>
</item>
<item>
<title>What are best hardware/software for automated back-up to external hard drive?</title>
<link>https://qanda.digipres.org/949/what-hardware-software-automated-back-external-hard-drive</link>
<description>I'm wondering if we as a digipres community have centered on one or a few trusted solutions for ongoing, automated backup of personal data to physical media, i.e., external hard drives. I'm interested in hardware and software recommendations for a Windows environment. This would be active research data management, and the data is potentially valuable for the long-term. Any data identified for long-term preservation would be migrated to a trusted repository. Please, if there's anyone out there who can help me hone in on some trusted solutions of the zillions of options that seem to be out there in the PC world, I'd be much appreciative.</description>
<guid isPermaLink="true">https://qanda.digipres.org/949/what-hardware-software-automated-back-external-hard-drive</guid>
<pubDate>Tue, 09 Jun 2015 21:39:20 +0000</pubDate>
</item>
<item>
<title>Recommendations - Drives for Offline Storage</title>
<link>https://qanda.digipres.org/930/recommendations-drives-for-offline-storage</link>
<description>I'm looking into options for drives for 'cold' storage for my institution, possibly for long periods of time (we would like a shelf-life of about four years). &amp;nbsp;They don't need to be particularly fast so much as reliable and long-lived (and, of course, cost-effective). &amp;nbsp;We've already got some LTO tape we use; we're looking more for hard disk drives or solid state drives to be held offline in a climate-controlled area. &amp;nbsp;The scenario involves a write-once, read-a-few-times situation.&lt;br /&gt;
&lt;br /&gt;
So, first of all, does anybody have any experiences or know of any studies about the longevity and data integrity of HDD versus SSD? &amp;nbsp;I know, for example, that SSD is better-equipped for unpowered storage than HDD, but that they can also be more prone to data loss.&lt;br /&gt;
&lt;br /&gt;
Second, does anybody have a particular brand that they use and would particularly recommend to purchase or to avoid?&lt;br /&gt;
&lt;br /&gt;
If you'd rather not answer on-list, you can email me at sarah.barsness@mnhs.org and I'll post your replies to this thread anonymously for you (I could *really* use some very candid recommendations).</description>
<guid isPermaLink="true">https://qanda.digipres.org/930/recommendations-drives-for-offline-storage</guid>
<pubDate>Thu, 04 Jun 2015 18:36:34 +0000</pubDate>
</item>
<item>
<title>Preserving PDF files with multimedia content</title>
<link>https://qanda.digipres.org/918/preserving-pdf-files-with-multimedia-content</link>
<description>I am curious what other insitutions are doing for PDF files with embedded video or audio content? We migrate almost all of our PDF's to PDF/A. The PDF/A stadard does not allow for embedded content like this.&lt;br /&gt;
&lt;br /&gt;
We have discussed normalizing the file to ensure long term usability but not to PDF/A or extracting the embedded content and handling them seperately. But this takes them out of their original presentation.&lt;br /&gt;
&lt;br /&gt;
Are there other options?&lt;br /&gt;
&lt;br /&gt;
Thanks.</description>
<guid isPermaLink="true">https://qanda.digipres.org/918/preserving-pdf-files-with-multimedia-content</guid>
<pubDate>Wed, 20 May 2015 20:24:50 +0000</pubDate>
</item>
<item>
<title>How to distinguish 68k and PPC executables on classic Macintoshes?</title>
<link>https://qanda.digipres.org/865/how-distinguish-68k-and-ppc-executables-classic-macintoshes</link>
<description>When getting a binary for a classic Macintosh operating system (up until version 9), how to distinguish for which processor architecture the binary was made?</description>
<guid isPermaLink="true">https://qanda.digipres.org/865/how-distinguish-68k-and-ppc-executables-classic-macintoshes</guid>
<pubDate>Thu, 26 Mar 2015 18:48:45 +0000</pubDate>
</item>
<item>
<title>Scanned manuscript - saved as TIFF image files in archival disc. Is it Ok</title>
<link>https://qanda.digipres.org/836/scanned-manuscript-saved-tiff-image-files-archival-disc-ok</link>
<description></description>
<guid isPermaLink="true">https://qanda.digipres.org/836/scanned-manuscript-saved-tiff-image-files-archival-disc-ok</guid>
<pubDate>Mon, 16 Feb 2015 19:58:42 +0000</pubDate>
</item>
<item>
<title>Any LTP &quot;Packaging Format&quot; Standard you Support that Makes More Sense than WARC?</title>
<link>https://qanda.digipres.org/830/packaging-format-standard-support-makes-more-sense-than-warc</link>
<description>&lt;p&gt;
	Here's my question:&amp;nbsp;&lt;strong&gt;Do you prefer a packaging format other than WARC? What other justifications should I take into account? Could you share additional resources for my consideration ( in addition to those below?)&amp;nbsp;&lt;/strong&gt;And I'll elaborate:&lt;/p&gt;
&lt;p&gt;
	We generally agree that digital permanent records should be kept in open and supported format (tools and communities). We even have a broad selection of formats to chose from (from TIFF/JPEG2000 through PDF/A to XML). What remains, in my view, is a similar broad agreement on the package format that house the above content and linked metadata. The target here is the format of the container, wrapper, or capsule.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	There are many requirements that this container should meet, and by far, I like that the container be extendable whereby one can add more content, additional metadata, user contributed context, etc.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	Sofar though, .zip container has more or less led the charge, though other formats such as .warc are emerging from studies and comparaisons and showing more promise, which prompts me to ask:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
	&lt;strong&gt;Do you prefer a packaging format other than WARC? What other justifications should I take into account? Could you share additional resources I could consider in addition to these below?&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
		Recommendations/studies supporting WARC
		&lt;ul&gt;
			&lt;li&gt;
				For web objects:&amp;nbsp;&lt;a href=&quot;http://www.getpocket.com/a/read/777166755&quot; rel=&quot;nofollow&quot;&gt;http://www.getpocket.com/a/read/777166755&lt;/a&gt;&lt;/li&gt;
			&lt;li&gt;
				For all objects:&amp;nbsp;&lt;a href=&quot;https://fedora.phaidra.univie.ac.at/fedora/get/o:293682/bdef:Content/get&quot; rel=&quot;nofollow&quot;&gt;https://fedora.phaidra.univie.ac.at/fedora/get/o:293682/bdef:Content/get&lt;/a&gt;&lt;/li&gt;
		&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;
		Standard using ZIP as container/wrapper/capsule:
		&lt;ul&gt;
			&lt;li&gt;
				Victorian Electronic Records Strategy / VERS Encapsulated Object (VEO) :&amp;nbsp;&lt;a href=&quot;http://prov.vic.gov.au/wp-content/uploads/2014/05/VERSStdRevisionProposal-v1-0.pdf&quot; rel=&quot;nofollow&quot;&gt;http://prov.vic.gov.au/wp-content/uploads/2014/05/VERSStdRevisionProposal-v1-0.pdf&lt;/a&gt;&lt;/li&gt;
		&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;
		Standard-to-be considering SIRF or an unspecified format (needs proof of concept)
		&lt;ul&gt;
			&lt;li&gt;
				Storage Industry Networking Association's SIRF (Self-Contained Information Retention Format (&amp;nbsp;&lt;a href=&quot;http://www.snia.org/SIRF&quot; rel=&quot;nofollow&quot;&gt;http://www.snia.org/SIRF&lt;/a&gt;&amp;nbsp;; )&lt;/li&gt;
		&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
	Answers, links and comments will be well received!&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/830/packaging-format-standard-support-makes-more-sense-than-warc</guid>
<pubDate>Fri, 13 Feb 2015 21:20:18 +0000</pubDate>
</item>
<item>
<title>Tool(s) for extracting administrative metadata from WARC?</title>
<link>https://qanda.digipres.org/779/tool-s-for-extracting-administrative-metadata-from-warc</link>
<description>I'm researching best practices for administrative metadata--preservation metadata in particular--for web archives. So far I've found some very helpful rationales and schemas, all PREMIS-in-METS-based, but I haven't seen anything that directly explains how one gets from point A to point B. That is, I haven't seen any descriptions of the steps nor the tools used to actually extract this type of metadata (or as much as can reasonably be gleaned) from WARCs. Have you? Have you extracted administrative metadata from your WARCs and lived to tell the tale? I'd love to know what you used and what you thought of the process.</description>
<guid isPermaLink="true">https://qanda.digipres.org/779/tool-s-for-extracting-administrative-metadata-from-warc</guid>
<pubDate>Thu, 29 Jan 2015 07:08:14 +0000</pubDate>
</item>
<item>
<title>Optimal file sizes for access PDFs</title>
<link>https://qanda.digipres.org/751/optimal-file-sizes-for-access-pdfs</link>
<description>We have digitised a collection of old books, pamphlets, etc, which we will be making available as PDFs and as images through BookReader. The original files were scanned as TIFFs and will not be available to users. The PDFs we originally created were high quality and large file sizes; some over 100 &amp;nbsp;MB. Obviously, this is far too large to expect most users - which will be the public - to download. Is it better to split the larger files into smaller and retain the high quality? Or regenerate the PDFs into smaller, lower quality files? And in either case, what is the ideal maximum file size for cultural heritage-type PDFs available to the general public? Have not been able to find any recommended standards at all around this issue.</description>
<guid isPermaLink="true">https://qanda.digipres.org/751/optimal-file-sizes-for-access-pdfs</guid>
<pubDate>Sat, 24 Jan 2015 20:41:55 +0000</pubDate>
</item>
<item>
<title>Splitting PDFs while preserving quality</title>
<link>https://qanda.digipres.org/729/splitting-pdfs-while-preserving-quality</link>
<description>For easier presentation, we need to break some very large PDFs into smaller files (we already have the originals saved in TIFF format). However, when we do this via Adobe, the total file sizes get halved, e.g. a 600MB PDF results in 6 PDFs that total 300MB in size. Does this denote loss of quality? How do I check? And what's the best way to break large PDFs into smaller files without that loss of quality?&lt;br /&gt;
&lt;br /&gt;
I thought this info would be relatively easy to find on the Adobe web site or elsewhere, but no luck so far.</description>
<guid isPermaLink="true">https://qanda.digipres.org/729/splitting-pdfs-while-preserving-quality</guid>
<pubDate>Wed, 21 Jan 2015 19:18:52 +0000</pubDate>
</item>
<item>
<title>What preservation format for video to use when digitizing VHS tapes?</title>
<link>https://qanda.digipres.org/710/what-preservation-format-for-video-when-digitizing-vhs-tapes</link>
<description></description>
<guid isPermaLink="true">https://qanda.digipres.org/710/what-preservation-format-for-video-when-digitizing-vhs-tapes</guid>
<pubDate>Mon, 05 Jan 2015 19:57:23 +0000</pubDate>
</item>
</channel>
</rss>