<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Siegfried on SI 667 - Winter 2026</title><link>https://morskyjezek.github.io/si667-2026-activities/tags/siegfried/</link><description>Recent content in Siegfried on SI 667 - Winter 2026</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 21 Feb 2026 11:25:36 -0500</lastBuildDate><atom:link href="https://morskyjezek.github.io/si667-2026-activities/tags/siegfried/index.xml" rel="self" type="application/rss+xml"/><item><title>Lab 07 Key</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-07-key/</link><pubDate>Sat, 21 Feb 2026 11:25:36 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-07-key/</guid><description>&lt;h2 id="lab-guidance-and-solutions"&gt;Lab Guidance and Solutions&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Problem 1:&lt;/strong&gt; Create directories to use for the reports, which will be the basis of your PDI.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Use the &lt;code&gt;mkdir&lt;/code&gt; command to make two new directories in the course files folder, one titled &lt;code&gt;sf_out&lt;/code&gt; and the second &lt;code&gt;br_out&lt;/code&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Problem 2:&lt;/strong&gt; Running Siegfried. Siegfried is a useful tool to create an inventory and a bulk process for file characterization information. Run the command on the &lt;code&gt;PKG-web-files-small&lt;/code&gt; directory and output the reports to the &lt;code&gt;sf_out&lt;/code&gt; directory.&lt;/p&gt;</description></item><item><title>Lab 07: File Characterization with Siegfried and Brunnhilde</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-07/</link><pubDate>Thu, 12 Feb 2026 15:14:13 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-07/</guid><description>&lt;p&gt;This week&amp;rsquo;s lab questions are prompts that aim to guide you in the file inspection process and to reflect on the information that you can glean in this process. The problems below are designed to run on the course files, which you have previously downloaded, and that the directory is named &lt;code&gt;si667-2026-main&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Note: &lt;a href="https://morskyjezek.github.io/si667-2026-activities/guides/guide-running-sf-br/"&gt;this guide page on the course activities site demonstrates using Siegfried and Brunnhilde for file reporting and characterization&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Installing &amp; Running Brunnhilde on Windows</title><link>https://morskyjezek.github.io/si667-2026-activities/guides/guide-running-brunnhilde-windows/</link><pubDate>Mon, 10 Feb 2025 00:00:00 +0000</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/guides/guide-running-brunnhilde-windows/</guid><description>&lt;p&gt;&lt;a href="https://github.com/tw4l/brunnhilde#installation"&gt;Brunnhilde&lt;/a&gt; is a companion tool to &lt;a href="https://morskyjezek.github.io/si667-2026-activities/guides/guide-installing-sf-windows/"&gt;Siegfried&lt;/a&gt;, and Brunnhilde is very useful in creating reports from the inventory and file characterization data that Siegfried creates. While perhaps not essential, it is at this time a highly useful tool that can create reports that are useful for overall analysis of the files you’re working with, as well as a report to keep with the files as useful technical and provenance metadata.&lt;/p&gt;
&lt;h1 id="installation-step-by-step"&gt;Installation Step-By-Step&lt;/h1&gt;
&lt;ol&gt;
&lt;li&gt;Before you install Brunnhilde, you must have Python 3 installed and running. This is likely ready to go if you have completed SI 506. If not, you may need to do that first. Instructions for setting up Python 3 can be found &lt;a href="https://docs.python.org/3.9/using/windows.html"&gt;here&lt;/a&gt; and &lt;a href="https://code.visualstudio.com/docs/python/python-tutorial"&gt;here&lt;/a&gt;. If you prefer to run in a virtual environment, you can also do that. Once Python 3 is ready, proceed to the next step.&lt;/li&gt;
&lt;li&gt;Open up Visual Studio Code, and open a new Terminal pane there.&lt;/li&gt;
&lt;li&gt;At the terminal prompt, you can use the pip command to install Brunnhilde: &lt;code&gt;pip install brunnhilde&lt;/code&gt;.&lt;br&gt;
&lt;em&gt;If this doesn&amp;rsquo;t work, you can try running &lt;code&gt;pip&lt;/code&gt; as a module thus: &lt;code&gt;$ python -m pip isntall brunnhilde&lt;/code&gt;.&lt;/em&gt;
&lt;img src="https://morskyjezek.github.io/si667-2026-activities/guides/guide-running-brunnhilde-windows/brunnhilde-pip-install.png" alt="Installing brunnhilde using python pip install" title="Installing brunnhilde using python pip install"&gt;&lt;/li&gt;
&lt;li&gt;Now, you can call brunnhilde with the command &lt;code&gt;brunnhilde.py [arguments]&lt;/code&gt; as you would other python programs.&lt;br&gt;
&lt;em&gt;Note that you may need to run this as a &amp;ldquo;module&amp;rdquo;, something like this:&lt;/em&gt;&lt;br&gt;
&lt;code&gt;python -m brunnhilde [arguments]&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;</description></item><item><title>Installing Siegfried (1.11.4) on Windows (11)</title><link>https://morskyjezek.github.io/si667-2026-activities/guides/guide-installing-sf-windows/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/guides/guide-installing-sf-windows/</guid><description>&lt;p&gt;Siegfried is a tool that you can use to characterize files, which means that it will assist in creating information about the kinds of files in a given location, their fixity, and other basic preservation information. You can also use it to link file type characterizations to the major file type registries, including the PUID (PRONOM Unique Identifier), FDD (Library of Congress Format Description Documents), and MIME Types (Multipurpose Internet Media Extensions, sometimes called Media Types). The goal of this activity is to create shared, reliable, and documented file format designations, when possible, so that you know what kind of stored digital information your collection has in it.&lt;/p&gt;</description></item><item><title>Running Siegfried &amp; Brunnhilde</title><link>https://morskyjezek.github.io/si667-2026-activities/guides/guide-running-sf-br/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/guides/guide-running-sf-br/</guid><description>&lt;p&gt;This page contains the instructions for running tools that can help with file reporting. These are useful tools that can create some of the preservation description information, which might accompany an information package, and to create technical information that can be used for tracking file integrity and duplication.&lt;/p&gt;
&lt;h1 id="setup"&gt;Setup&lt;/h1&gt;
&lt;p&gt;The following sections show how to get set up to run the file reporting tools.&lt;/p&gt;
&lt;h2 id="sample-files"&gt;Sample Files&lt;/h2&gt;
&lt;p&gt;All of the activities will use the course&amp;rsquo;s sample files, which you should have previously downloaded during class in January. If you didn&amp;rsquo;t download them, have lost those files, or want a new copy, they are located in the course github repository, and you can download them all directly as a zip file at &lt;a href="https://github.com/morskyjezek/si667-2026"&gt;https://github.com/morskyjezek/si667-2026&lt;/a&gt;. Unzip that folder somewhere on your computer, for example in your &lt;code&gt;Desktop&lt;/code&gt; or &lt;code&gt;Documents&lt;/code&gt; folder. This should result in a folder named &lt;code&gt;si667-2026-main&lt;/code&gt;, which will match the demonstrations below. (&lt;em&gt;Nota bene: the screencasts below were recorded in 2023 and 2024, so some of the sections in the videos may show those years in its name, but assume any paths or other references should be to 2026.&lt;/em&gt;)&lt;/p&gt;</description></item></channel></rss>