<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Change log | museum-digital: blog</title>
	<atom:link href="https://blog.museum-digital.org/tag/changelog/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.museum-digital.org</link>
	<description>A blog on museum-digital and the broader digitization of museum work.</description>
	<lastBuildDate>Fri, 14 Feb 2025 10:24:05 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://blog.museum-digital.org/wp-content/uploads/2020/01/cropped-mdlogo-code-512px-32x32.png</url>
	<title>Change log | museum-digital: blog</title>
	<link>https://blog.museum-digital.org</link>
	<width>32</width>
	<height>32</height>
</image> 
<atom:link rel="search" type="application/opensearchdescription+xml" title="Search museum-digital: blog" href="https://blog.museum-digital.org/wp-json/opensearch/1.1/document" />	<item>
		<title>State of Dev, December 2024 &#038; January 2025</title>
		<link>https://blog.museum-digital.org/2025/02/14/state-of-dev-december-2024-january-2025/</link>
		
		<dc:creator><![CDATA[Joshua Ramon Enslin]]></dc:creator>
		<pubDate>Thu, 13 Feb 2025 23:48:42 +0000</pubDate>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Frontend]]></category>
		<category><![CDATA[Importer]]></category>
		<category><![CDATA[musdb]]></category>
		<category><![CDATA[nodac]]></category>
		<category><![CDATA[Batch editing]]></category>
		<category><![CDATA[Change log]]></category>
		<category><![CDATA[Controlled Vocabularies]]></category>
		<category><![CDATA[Imports]]></category>
		<category><![CDATA[New Features]]></category>
		<category><![CDATA[TEI]]></category>
		<category><![CDATA[Version control]]></category>
		<guid isPermaLink="false">https://blog.museum-digital.org/?p=4306</guid>

					<description><![CDATA[Once again a simple change log of the recent updates to museum-digital's different tools.]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">December 2024</h2>



<h3 class="wp-block-heading"><a href="https://de.about.museum-digital.org/software/frontend/">Frontend</a></h3>



<ul class="wp-block-list">
<li>Dates in <a href="https://de.wikipedia.org/wiki/Text_Encoding_Initiative">TEI</a> transcriptions are parsed, irrespective of whether <code>when=""</code> oder <code>when=''</code> was used</li>



<li>Notes for markings are now publicly displayed<br><em>This was missing thus far and is now implemented similar to how event notes are displayed. If a note exists, a small &#8220;[?]&#8221; appears behind the marking title line. Upon hovering over it, a tooltip appears with the relevant information.</em></li>
</ul>



<h3 class="wp-block-heading"><a href="https://de.about.museum-digital.org/software/musdb/">musdb</a></h3>



<ul class="wp-block-list">
<li>Names and descriptions of exhibitions and object groups can now be translated</li>



<li><a href="https://blog.museum-digital.org/2025/01/13/version-control-batch-transfer-between-data-fields-of-object-records/">Version control</a></li>



<li>Log of “current locations&#8221; of an object can be exported as a CSV file</li>



<li>Uploaded object images can now be hidden or published in one batch operation</li>



<li><a href="https://de.handbook.museum-digital.info/musdb/API/index.html">API</a> extended
<ul class="wp-block-list">
<li>(New functions)</li>



<li>Transfer object dimensions</li>



<li>List images and resources for an object</li>



<li>Image metadata</li>



<li>Publish / hide object images</li>
</ul>
</li>
</ul>



<h2 class="wp-block-heading">January 2025</h2>



<h3 class="wp-block-heading"><a href="https://de.about.museum-digital.org/software/frontend/">Frontend</a></h3>



<ul class="wp-block-list">
<li><em>Objects can now be sorted by the aesthetics of the thumbnail</em> (A dedicated blog post on this will follow soon)</li>
</ul>



<h2 class="wp-block-heading"><a href="https://de.about.museum-digital.org/software/musdb/">musdb</a></h2>



<ul class="wp-block-list">
<li><a href="https://blog.museum-digital.org/de/2025/01/13/versionierung-transfer-zwischen-datenfeldern/">Batch transfer between between free text fields of object data</a></li>



<li>Alignment of the maximum field length for notes on opening hours is now consistent between UI and database</li>



<li>Bug fixed with switching between institutions during consistency checks fixed (relevant only to users with administrative access to multiple museums)</li>



<li>Literature can now be searched by editors</li>
</ul>



<h3 class="wp-block-heading"><a href="https://blog.museum-digital.org/de/category/technik-design/importer-de/">Importer</a></h3>



<ul class="wp-block-list">
<li>Core
<ul class="wp-block-list">
<li>Automatic transformation of life dates for actors
<ul class="wp-block-list">
<li>Year of death “01.01.2012” now becomes “2012”, instead of 01.01 as before</li>
</ul>
</li>



<li>&#8220;?&#8221; and &#8220;(?)&#8221; are removed from the beginning and end of imported keywords</li>



<li>Various types of brackets in keyword names are converted to regular brackets</li>
</ul>
</li>



<li>Parser
<ul class="wp-block-list">
<li>Stricter internal implementation of settings, all imports can now implement the <code>start_at</code> setting
<ul class="wp-block-list">
<li>This is particularly useful for the repeated execution of imports that abort due to new, previously uncovered elements and other debugging.</li>
</ul>
</li>



<li>New parsers:
<ul class="wp-block-list">
<li><a href="https://de.wikipedia.org/wiki/Metadata_Object_Description_Schema">MODS</a> (mainly used in library contexts)</li>



<li>Parser for Exports from Faust for the <a href="https://st.museum-digital.de/institution/87">Händel-Haus</a></li>



<li>Parser for XML dumps from MuseumPlus Classic (MsSQL > XML export per table > Import)</li>



<li>Bugfixes
<ul class="wp-block-list">
<li>Field “Verwender” in Primus parser was mapped to production events</li>



<li>Material / technology are now imported correctly in the parser for BeeCollect exports for the Industrial Museums of Saxony</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>



<li>„Frontend“
<ul class="wp-block-list">
<li>CLI now also has options for switching off the import of individual areas</li>



<li>Help text for command line tool</li>
</ul>
</li>
</ul>



<h3 class="wp-block-heading"><a href="https://de.about.museum-digital.org/software/nodac/">nodac</a></h3>



<ul class="wp-block-list">
<li>Splitting of keywords now also recognizes keywords that should be split into places, times, etc.
<ul class="wp-block-list">
<li>Bsp.: „Helm; Berlin“ > Schlagwort „Helm“ + Ort „Berlin“</li>



<li>Example: “helmet; Berlin” > keyword “helmet” + place “Berlin”</li>
</ul>
</li>



<li>When searching for keywords with ambiguous names, both keywords and generally ambiguous terms are now taken into account</li>



<li>Times can now be merged with others directly from the time edit page</li>
</ul>



<div class="wp-block-cgb-cc-by message-body" style="background-color:white;color:black"><img decoding="async" src="https://blog.museum-digital.org/wp-content/plugins/creative-commons/includes/images/by.png" alt="CC" width="88" height="31"/><p><span class="cc-cgb-name">This content</span> is licensed under a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license.</a> <span class="cc-cgb-text"></span></p></div>
]]></content:encoded>
					
		
		
		<post-thumbnail><url>https://blog.museum-digital.org/wp-content/uploads/2025/02/typing-2025-01.avif</url><width>600</width><height>336</height></post-thumbnail>	</item>
		<item>
		<title>State of Development, November 2024: &#8220;Real&#8221; separated Measurements and a Better Recognition of Tags, Places, etc.</title>
		<link>https://blog.museum-digital.org/2025/01/13/state-of-development-november-2024-real-separated-measurements-and-a-better-recognition-of-tags-places-etc/</link>
		
		<dc:creator><![CDATA[Joshua Ramon Enslin]]></dc:creator>
		<pubDate>Mon, 13 Jan 2025 13:41:45 +0000</pubDate>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Frontend]]></category>
		<category><![CDATA[Importer]]></category>
		<category><![CDATA[musdb]]></category>
		<category><![CDATA[Change log]]></category>
		<category><![CDATA[New Features]]></category>
		<guid isPermaLink="false">https://blog.museum-digital.org/?p=4255</guid>

					<description><![CDATA[A short overview in list form of the recent technical updates around museum-digital, as of November 2024.]]></description>
										<content:encoded><![CDATA[
<p>musdb</p>



<ul class="wp-block-list">
<li>Basic re-implementation of separated measurements for objects (tab: &#8220;addendum&#8221;)</li>



<li>The type of measurement (width, length, etc.) is now managed using a controlled list, which can easily be extended. This also allows for measurement types of different levels of specificity (&#8220;width&#8221; vs. &#8220;width of socle&#8221;)</li>



<li>The new implementation allows users to identify whether a measurement is exact and add notes for each measurement</li>



<li>Measured values now need to be entered as a floating point number &#8211; consistent search for objects smaller or larger than a given size is thus made possible (previously only available for entries where the system could deduce a numeric value from whatever had been entered)</li>



<li>Unique naming components of entered tags are automatically parsed into a relation type. German: &#8220;Apfel (Motiv)&#8221; is automatically split into the tag &#8220;Apple&#8221; and the relation type &#8220;display subject&#8221;.</li>



<li>Users entering a tag with such a naming component that is known to belong to another vocabulary will have their input auto-corrected to reflect both. Entering the tag &#8220;Berlin (Motiv)&#8221; will be auto-corrected to a link to a &#8220;displayed place&#8221; &#8220;Berlin&#8221;.</li>



<li>The list of spaces that can be linked to an object as its current location is now sorted alphabetically</li>
</ul>



<p>Frontend</p>



<ul class="wp-block-list">
<li>Re-implemented separated Measurements</li>
</ul>



<p>Import</p>



<ul class="wp-block-list">
<li>The import tool now also uses the new implementation of separated measurements</li>



<li>Unique naming components of entered tags are automatically parsed into a relation type. German: &#8220;Apfel (Motiv)&#8221; is automatically split into the tag &#8220;Apple&#8221; and the relation type &#8220;display subject&#8221;.</li>



<li>Users entering a tag with such a naming component that is known to belong to another vocabulary will have their input auto-corrected to reflect both. Entering the tag &#8220;Berlin (Motiv)&#8221; will be auto-corrected to a link to a &#8220;displayed place&#8221; &#8220;Berlin&#8221;.</li>



<li>Links between two objects are now imported using the dedicated data type for this purpose. They had previously been imported as regular web links.</li>
</ul>



<p>nodac</p>



<ul class="wp-block-list">
<li>When merging two entries, links between the entries and collections, exhibitions, etc. are now reflected and rewritten</li>



<li>previously, links to such data types prevented the completion of the merge</li>



<li>If an entry&#8217;s name is marked to always belong to e.g. a tag, the buttons for transferring the entry to the actor, place, or time vocabularies are now hidden.</li>



<li>If an entry is moved between vocabularies, links between the entry and objects as &#8220;display subject&#8221; / &#8220;displayed place&#8221; / &#8220;displayed actor&#8221; are reflected and translated into new links using the appropriate link type.</li>



<li>A new context menu on overview pages allows for a quick access to functionalities like the splitting of entries</li>
</ul>
]]></content:encoded>
					
		
		
		<post-thumbnail><url>https://blog.museum-digital.org/wp-content/uploads/2025/01/a-1.avif</url><width>600</width><height>338</height></post-thumbnail>	</item>
		<item>
		<title>State of Development, October 2024: Searching Objects Currently On Exhibition, Linking Location and Acquisition of Literature</title>
		<link>https://blog.museum-digital.org/2024/11/06/state-of-development-october-2024-searching-objects-currently-on-exhibition-linking-location-and-acquisition-of-literature/</link>
		
		<dc:creator><![CDATA[Joshua Ramon Enslin]]></dc:creator>
		<pubDate>Wed, 06 Nov 2024 12:58:01 +0000</pubDate>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[Frontend]]></category>
		<category><![CDATA[Importer]]></category>
		<category><![CDATA[musdb]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[Change log]]></category>
		<category><![CDATA[Object images]]></category>
		<category><![CDATA[Object search (musdb)]]></category>
		<guid isPermaLink="false">https://blog.museum-digital.org/?p=4194</guid>

					<description><![CDATA[After the blog has been very quiet this year with regard to the technical development of museum-digital, we are now trying to publish the summaries of new developments &#8211; enriched with screenshots &#8211; that are prepared for the monthly “regional administrators” rounds in Germany anyway. These are in the form of listings, and this is <a href="https://blog.museum-digital.org/2024/11/06/state-of-development-october-2024-searching-objects-currently-on-exhibition-linking-location-and-acquisition-of-literature/" class="more-link">...</a>]]></description>
										<content:encoded><![CDATA[
<p>After the blog has been very quiet this year with regard to the technical development of museum-digital, we are now trying to publish the summaries of new developments &#8211; enriched with screenshots &#8211; that are prepared for the monthly “regional administrators” rounds in Germany anyway. </p>



<p>These are in the form of listings, and this is how it should be here too.</p>



<h2 class="wp-block-heading"><a href="https://de.about.museum-digital.org/software/frontend/">Frontend</a></h2>



<h3 class="wp-block-heading">Features &amp; Improvements</h3>



<ul class="wp-block-list">
<li>Some improvements in background scripts, especially better handling of timeouts when calculating “Similar objects” in very large instances</li>



<li>Contributors, linked locations and times for an object group are now listed alphabetically by name</li>



<li>Table headers for event components (who, when, where) are now only displayed in the A4 PDF if there is also content for the row</li>



<li>New search option for object searches: “Is currently on display”</li>



<li>Links to the Themator now use the new URL scheme of the Themator<br>(<a href="https://themator.museum-digital.de/t/690">https://themator.museum-digital.de/t/690</a> instead of <a href="https://themator.museum-digital.de/ausgabe/showthema.php?m_tid=690&amp;tid=690">https://themator.museum-digital.de/ausgabe/showthema.php?m_tid=690&amp;tid=690</a>)</li>
</ul>



<figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex">
<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" width="826" height="459" data-id="4185" src="https://blog.museum-digital.org/wp-content/uploads/2024/11/frontend_Suche_verfeinern.png.avif" alt="Screenshot aus dem Frontend von museum-digital." class="wp-image-4185" srcset="https://blog.museum-digital.org/wp-content/uploads/2024/11/frontend_Suche_verfeinern.png.avif 826w, https://blog.museum-digital.org/wp-content/uploads/2024/11/frontend_Suche_verfeinern.png-300x167.avif 300w" sizes="(max-width: 826px) 100vw, 826px" /><figcaption class="wp-element-caption">The new filter option “Currently on display” in the overlay for the advanced search for objects in the frontend of museum -digital.</figcaption></figure>



<figure class="wp-block-image size-large"><img decoding="async" width="548" height="583" data-id="4184" src="https://blog.museum-digital.org/wp-content/uploads/2024/11/frontend_MItwirkende_sortiert.png.avif" alt="Screenshot aus dem Frontend von museum-digital." class="wp-image-4184" srcset="https://blog.museum-digital.org/wp-content/uploads/2024/11/frontend_MItwirkende_sortiert.png.avif 548w, https://blog.museum-digital.org/wp-content/uploads/2024/11/frontend_MItwirkende_sortiert.png-282x300.avif 282w" sizes="(max-width: 548px) 100vw, 548px" /><figcaption class="wp-element-caption">The contributors to an object group are now sorted alphabetically by sorted by name .</figcaption></figure>
</figure>



<h3 class="wp-block-heading">Bugfixes</h3>



<ul class="wp-block-list">
<li>Error when searching for controlled list terms that contained multiple spaces via the “Refine search” overlay (search for license “Public Domain Mark”)</li>



<li>Exactness setting in the “refine search” overlay was not transferred to the actual search query</li>



<li>Simple embedding of an object (analogous to YouTube videos, for example; accessible via the “Cite” menu of an object page) had various errors / now works again</li>
</ul>



<h2 class="wp-block-heading"><a href="https://de.about.museum-digital.org/software/musdb/">musdb</a></h2>



<h3 class="wp-block-heading">Features &amp; Improvements</h3>



<ul class="wp-block-list">
<li>In the API documentation of musdb there is now a note that the frontend also has an API
<ul class="wp-block-list">
<li>Frontend API
<ul class="wp-block-list">
<li>You do not need to authenticate yourself to use the frontend API</li>



<li>The frontend API tends to be faster and easier to use</li>



<li>Is read-only</li>
</ul>
</li>



<li>musdb API
<ul class="wp-block-list">
<li>Can do more: Can also see non-public stocks and fields / data types</li>



<li>Is much more granular (more queries for the same data, but you likely get exactly the data you are looking for instead of e.g. all data known about a given object)</li>



<li>Can be used for writing data</li>
</ul>
</li>
</ul>
</li>



<li>Suggestion lists when searching for vocabulary terms in the side column of the object search page have been revised
<ul class="wp-block-list">
<li>Tooltips appear when hovering over</li>



<li>Implementation in Vanilla JS, removing jQuery</li>



<li>(this means significantly better performance of the search results list in list format, because jQuery no longer needs to be loaded)</li>
</ul>
</li>
</ul>



<ul class="wp-block-list">
<li></li>
</ul>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="416" height="1024" src="https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Tooltip_in_Auswahlliste.png-416x1024.avif" alt="Screenshot aus musdb." class="wp-image-4188" srcset="https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Tooltip_in_Auswahlliste.png-416x1024.avif 416w, https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Tooltip_in_Auswahlliste.png-122x300.avif 122w, https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Tooltip_in_Auswahlliste.png.avif 714w" sizes="auto, (max-width: 416px) 100vw, 416px" /><figcaption class="wp-element-caption">The suggestion lists for places, times, persons and keywords in the quick search function of the object search mask have been re-implemented. The main visible benefit is that explanations now appear directly when hovering over the terms in the list.</figcaption></figure>



<ul class="wp-block-list">
<li>User page / Login
<ul class="wp-block-list">
<li>Log of logins now also with IP and user agents</li>



<li>Login via login persisted in the browser (“Remember me”) is logged and displayed</li>



<li>All browsers permanently logged in via cookie are forced to log in again after a password change</li>



<li>New option to invalidate all remembered logins on other devices (browser must be logged in again)</li>
</ul>
</li>
</ul>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="694" src="https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Login_log.png-1024x694.avif" alt="Screenshot aus musdb." class="wp-image-4186" srcset="https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Login_log.png-1024x694.avif 1024w, https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Login_log.png-300x203.avif 300w, https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Login_log.png-1536x1041.avif 1536w, https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Login_log.png.avif 1762w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">The “Login log” in the account settings can be used to track when and in what context one&#8217;s own user account was accessed in musdb. This allows for the identification of account takeovers by third parties. Newly logged and/or displayed are: IP address used to log in, the user agent (identification of the browser) and whether the browser was automatically logged in via a permanent login cookie (“Remember me”).</figcaption></figure>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="942" height="678" src="https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_User_Erinnerte_Logins_loeschen.png.avif" alt="Screenshot aus musdb." class="wp-image-4189" srcset="https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_User_Erinnerte_Logins_loeschen.png.avif 942w, https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_User_Erinnerte_Logins_loeschen.png-300x216.avif 300w" sizes="auto, (max-width: 942px) 100vw, 942px" /><figcaption class="wp-element-caption">A new button in the toolbar of the account settings in musdb allows you to log out all permanently logged in browsers / devices from your own account.</figcaption></figure>



<ul class="wp-block-list">
<li>Object
<ul class="wp-block-list">
<li>More restrictions for the publication of object data records.</li>



<li>An object can no longer be published if:
<ul class="wp-block-list">
<li>&#8230; the object name is the same as the object description</li>



<li>&#8230; the description contains the character string “lorem ipsum”</li>
</ul>
</li>



<li>When object entries are unpublished / hidden, the images linked to the image are renamed (thus invalidating links to the images). When publishing the object again, this is reversed so that existing links work again.</li>



<li>Spaces in selection lists are now listed alphabetically as the actual location when linking</li>
</ul>
</li>



<li>Literature
<ul class="wp-block-list">
<li>Acquisitions can now be linked to literature
<ul class="wp-block-list">
<li>Previous owners etc. can thus be linked to a literature entry</li>
</ul>
</li>



<li>Spaces (actual location) can be linked to literature</li>
</ul>
</li>
</ul>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="504" src="https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Reiter_Verwaltung.png-1024x504.avif" alt="Screenshot aus musdb." class="wp-image-4187" srcset="https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Reiter_Verwaltung.png-1024x504.avif 1024w, https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Reiter_Verwaltung.png-300x148.avif 300w, https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Reiter_Verwaltung.png-1536x756.avif 1536w, https://blog.museum-digital.org/wp-content/uploads/2024/11/musdb_Reiter_Verwaltung.png.avif 1800w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Via the new tab “Administration” tab on tab on the literature editing page, the location and access context of the literature entry can be linked. This can be useful if the literature module is also used to manage the museum library. is also used to manage the museum library .</figcaption></figure>



<h3 class="wp-block-heading">Bugfixes</h3>



<ul class="wp-block-list">
<li>Overlay for setting searches for objects: Multi-word search terms were converted into multiple searches instead of being searched as a string of words (“red helmet” &gt; “red” AND “helmet” instead of “red helmet”)</li>



<li>Error when searching for controlled list terms that contained multiple spaces via the “Refine search” overlay (search for license “Public Domain Mark”)</li>
</ul>



<h2 class="wp-block-heading"><a href="https://blog.museum-digital.org/de/category/technik-design/importer-de/">Importer</a></h2>



<ul class="wp-block-list">
<li>Link between literature and spaces (actual location) as well as acquisitions is implemented in the &#8220;core&#8221; of the import tool</li>



<li>ImageByInvno parser (assignment of images to objects via inventory numbers contained in the file name) can now be used to import PDF files</li>
</ul>



<h2 class="wp-block-heading"><a href="https://files.museum-digital.org/">files.museum-digital.org</a></h2>



<ul class="wp-block-list">
<li>Added a small script to enhance PDF metadata based on an XML sidecar file. See e.g.: <a href="https://files.museum-digital.org/de/Praesentationen/2024-10-18_md-deutschland-eV-stellt-sich-vor_Usertreffen_MA.xml">https://files.museum-digital.org/de/Praesentationen/2024-10-18_md-deutschland-eV-stellt-sich-vor_Usertreffen_MA.xml</a></li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p>Main post image generated using illustriousXL_smoothftSPO</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<div class="wp-block-cgb-cc-by message-body" style="background-color:white;color:black"><img loading="lazy" decoding="async" src="https://blog.museum-digital.org/wp-content/plugins/creative-commons/includes/images/by.png" alt="CC" width="88" height="31"/><p><span class="cc-cgb-name">This content</span> is licensed under a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license.</a> <span class="cc-cgb-text"></span></p></div>
]]></content:encoded>
					
		
		
		<post-thumbnail><url>https://blog.museum-digital.org/wp-content/uploads/2024/11/banner.png.avif</url><width>600</width><height>336</height></post-thumbnail>	</item>
	</channel>
</rss>
