<?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>Location tracking | museum-digital: blog</title>
	<atom:link href="https://blog.museum-digital.org/tag/location-tracking/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>Sun, 07 May 2023 16:44:43 +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>Location tracking | 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>Summary of the monthly user meetup (April 2023) / New features and improvements</title>
		<link>https://blog.museum-digital.org/2023/05/07/summary-of-the-monthly-user-meetup-april-2023-new-features-and-improvements/</link>
		
		<dc:creator><![CDATA[Joshua Ramon Enslin]]></dc:creator>
		<pubDate>Sun, 07 May 2023 16:44:42 +0000</pubDate>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[Frontend]]></category>
		<category><![CDATA[musdb]]></category>
		<category><![CDATA["List results"]]></category>
		<category><![CDATA[Imports]]></category>
		<category><![CDATA[Location tracking]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[User interface]]></category>
		<guid isPermaLink="false">https://blog.museum-digital.org/?p=3731</guid>

					<description><![CDATA[We continued the series of monthly user meetups and again discussed the new features and improvements. A summary can be found below. New Developments The last month has been an exceptionally slow month in terms of technical development around museum-digital. There are however some newsworthy tidbits. musdb Recording external IDs for museums Museums, like all <a href="https://blog.museum-digital.org/2023/05/07/summary-of-the-monthly-user-meetup-april-2023-new-features-and-improvements/" class="more-link">...</a>]]></description>
										<content:encoded><![CDATA[
<p>We continued the series of monthly user meetups and again discussed the new features and improvements. A summary can be found below.</p>



<h2 class="wp-block-heading" id="h-new-developments">New Developments</h2>



<p>The last month has been an exceptionally slow month in terms of technical development around museum-digital. There are however some newsworthy tidbits.</p>



<h3 class="wp-block-heading" id="h-musdb">musdb</h3>



<h4 class="wp-block-heading" id="h-recording-external-ids-for-museums">Recording external IDs for museums</h4>



<p>Museums, like all of us, are present in more and more databases. For linking different databases, it is useful &#8211; sometimes necessary &#8211; to know the ID of the same entity in both databases. Hungarian law thus mandates collection management systems, which are to be accredited for fully paperless use in museums, to allow storing a museum&#8217;s ID with the Hungarian Statistical Office. musdb can now do exactly that: Store external IDs of museums in a given list of external source repositories / databases.</p>



<p>The list of available external databases and the regular expressions to validate IDs in them are available <a href="http://The list of available external databases and the regular expressions to validate IDs in them are available here. For now, the list only contains the Hungarian Statistical Office, but the more options there will be in the future, the better.">here</a>. For now, the list only contains the Hungarian Statistical Office, but the more options there will be in the future, the better.</p>



<h4 class="wp-block-heading" id="h-more-fields-covered-by-list-results-and-excel-export">More fields covered by &#8220;list results&#8221; and Excel export</h4>



<p>The &#8220;list results&#8221; page (a.k.a. table view) for object search results offers the option to view the selected objects&#8217; data in a customizable tabular format. Mainly because of that exact tabular format, it is not possible to display everything a full database view of the object offers using the &#8220;list results&#8221; page. Over the last month, we have nevertheless extended the list of displayable fields in the &#8220;list results&#8221; table.</p>



<p>Thus, it is now possible to display all translations for the object type, object name, descriptions, etc. of an object. Similarly, it is now possible to list all Weblinks linked to the object as a compiled (comma-separated) field. As the automated report generation and the Excel export tools build upon the same basic code as the &#8220;list results&#8221; page, these new fields are now also available in those cases.</p>



<h4 class="wp-block-heading" id="h-new-field-for-objects-last-change-of-permanent-location">New field for objects: &#8220;Last change of permanent location&#8221;</h4>



<p>It is now possible to manually record the last date, the permanent location of a given object has been updated. This obviously makes sense for tracking relocations and re-organizations within the museum. Importantly, the field needs to be manually filled out, as the date of the last change of the permanent location may be far in the past or frankly unrelated to the database, even if there is one (say, the museum moves the depot to a different place, but the date is only later updated in the database via a batch editing process).</p>



<h4 class="wp-block-heading" id="h-user-interface">User interface</h4>



<p>After there were some reports of people not seeing the difference between a valid form in musdb and an invalid / incomplete one, we updated the design of submit buttons. Submit buttons in incomplete forms are now blurred out, to add another hint at the incompleteness of the form.</p>



<h3 class="wp-block-heading" id="h-frontend">Frontend</h3>



<h4 class="wp-block-heading" id="h-improved-performance-and-decreased-bandwidth-usage-serving-images-in-webp">Improved performance and decreased bandwidth usage: serving images in webp</h4>



<p>Over the last years, there have been a number of new image formats seeking to combine all the features of older and well-established formats like JPG and PNG with an improved compression. The most established format of that newer generation of image formats is <a href="https://en.wikipedia.org/wiki/WebP">webp</a>, which is by now well-supported by all modern browsers and most local image viewers.</p>



<p>To save bandwidth and improve loading speed, we now store and serve full-sized webp versions of newly uploaded object images along with the regular jpg versions. If possible, the webp version is served on object pages. An additional benefit is the aforementioned support for features jpg files do not support, such as transparent image backgrounds.</p>



<h4 class="wp-block-heading" id="h-iframe-embedding-now-only-possible-from-whitelisted-sources">iFrame embedding now only possible from whitelisted sources</h4>



<p>If a museum wants to embed their data from museum-digital into their own website, there are traditionally two ways to do so. The better, but much more complicated option is to use the API to fetch the relevant data and present them in any way one wants. Much easier (and cheaper obviously) is embedding the museum&#8217;s data using iframes.</p>



<p>Unfortunately, iframes can also be used for attacks on users&#8217; login data. We have thus now restricted this option to only allow embedding from whitelisted sources. If a museum wants to embed their data this way, this means that they now need to notify their regional administrators beforehand.</p>



<h3 class="wp-block-heading" id="h-importer">Importer</h3>



<p>The importer now supports imports for exports from Startext&#8217;s <a href="https://www.startext.de/produkte/hida">HiDa</a> in the configuration of the Saxon State Agency for Museums.</p>



<h2 class="wp-block-heading">Other News</h2>



<p>In other news, the <a href="https://www.youtube.com/@museum-digital/">Youtube</a> channel has picked up steam, with some new tutorials both in German and Ukrainian.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Shipments and Acquisitions in musdb</title>
		<link>https://blog.museum-digital.org/2023/02/09/transports-and-acquisitions-in-musdb/</link>
					<comments>https://blog.museum-digital.org/2023/02/09/transports-and-acquisitions-in-musdb/#respond</comments>
		
		<dc:creator><![CDATA[Joshua Ramon Enslin]]></dc:creator>
		<pubDate>Thu, 09 Feb 2023 18:31:35 +0000</pubDate>
				<category><![CDATA[musdb]]></category>
		<category><![CDATA[Acquisitions]]></category>
		<category><![CDATA[Collection management]]></category>
		<category><![CDATA[Location tracking]]></category>
		<category><![CDATA[New Features]]></category>
		<category><![CDATA[Object search (musdb)]]></category>
		<category><![CDATA[Shipments]]></category>
		<guid isPermaLink="false">https://blog.museum-digital.org/?p=3541</guid>

					<description><![CDATA[In one transaction, a museum buys 50 objects at an auction price for 3600 Euro. What is the price of a single one of the objects in the transaction? Realistically there is none. But musdb required one to enter a price for the acquisition of each single object thus far. Hence, users were left with <a href="https://blog.museum-digital.org/2023/02/09/transports-and-acquisitions-in-musdb/" class="more-link">...</a>]]></description>
										<content:encoded><![CDATA[
<p>In one transaction, a museum buys 50 objects at an auction price for 3600 Euro. What is the price of a single one of the objects in the transaction?</p>



<p>Realistically there is none. But <a href="https://en.about.museum-digital.org/software/musdb/">musdb</a> required one to enter a price for the acquisition of each single object thus far. Hence, users were left with no choice but to make up the price or to not enter one at all.</p>



<p>This problem is now solved, as is the tracking of shipments. Both of these are completely new sections of musdb that can be linked to objects (and in the case of shipments, exhibitions and loans as well).</p>



<h2 class="wp-block-heading" id="acquisitions">Acquisitions</h2>



<p>To access the acquisitions section in musdb, one can use the theee dots symbol in the main navigation (at the very top of a page) or enable the link to this section using the personal settings (accessible by clicking on one&#8217;s name).</p>



<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" width="1024" height="531" src="https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-menu-acquisitions-shipments-1024x531.webp" alt="" class="wp-image-3552" srcset="https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-menu-acquisitions-shipments-1024x531.webp 1024w, https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-menu-acquisitions-shipments-300x156.webp 300w, https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-menu-acquisitions-shipments-1536x796.webp 1536w, https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-menu-acquisitions-shipments.webp 1800w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Enabling menu items for acquisitions via the personal settings</figcaption></figure>



<p>Entering, filtering and searching acquisitions works roughly analogous to what one would do when managing loans.</p>



<figure class="wp-block-image size-large"><img decoding="async" width="1024" height="423" src="https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-All-acquisitions-1024x423.webp" alt="" class="wp-image-3550" srcset="https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-All-acquisitions-1024x423.webp 1024w, https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-All-acquisitions-300x124.webp 300w, https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-All-acquisitions-1536x635.webp 1536w, https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-All-acquisitions.webp 1800w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Filtering acquisitions</figcaption></figure>



<p>Importantly, acquisitions are linked to a source of previous owner of the acquisition and possibly a source for the funding required to actually acquire the objects. Both of these fields are controlled by the contacts list / address book.</p>



<p>On object editing pages, acquisition processes can be linked to the given object using the object administration tab. Here, &#8220;acquisition&#8221; is a newly available select fields right next to the older fields for the acquition date, price, and currency. Once an acquisition process has been linked, a preview of the acquisition process and &#8211; if available &#8211; a preview of the contact information of the previous owner / acquisition source are displayed right below the select field. These new previews are now also available if an owner of the object other than the museum itself has been entered by the way.</p>



<figure class="wp-block-image size-large"><img decoding="async" width="1024" height="666" src="https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-Acquisition-Preview-1024x666.webp" alt="" class="wp-image-3549" srcset="https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-Acquisition-Preview-1024x666.webp 1024w, https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-Acquisition-Preview-300x195.webp 300w, https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-Acquisition-Preview-1536x999.webp 1536w, https://blog.museum-digital.org/wp-content/uploads/2023/02/musdb-Acquisition-Preview.webp 1800w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Previews for acquisitions and previous owners are displayed on the administration tab</figcaption></figure>



<h2 class="wp-block-heading" id="shipments">Shipments</h2>



<p>Shipments can now be added, listed and tracked in a similar way to acquisitions. They, too, build a whole new section of musdb that can toggled into the shortcut navigation by way of the personal settings &#8211; or they can be accessed using the three dots symbol in the navigation at the very top right of the window.</p>



<p>While everything else in terms of adding, listing and updating shipments works roughly analogous to the management of acquisitions, shipments can be linked to objects via the object&#8217;s destination tab and they can be linked to exhibitions and loans. Hence, there are new tabs on the loans and exhibitions pages for listing the shipments linked to a given loan or exhibition.</p>



<p>Image credits: <a href="https://nat.museum-digital.de/institution/72">Kulturstiftung Sachsen-Anhalt &#8211; Kunstmuseum Moritzburg Halle (Saale)</a>: <a href="https://nat.museum-digital.de/object/32665">Frachtschiff im Hafen von Göteborg</a>, CC BY-NC-SA, photographer: Hans Finsler.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.museum-digital.org/2023/02/09/transports-and-acquisitions-in-musdb/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-thumbnail><url>https://blog.museum-digital.org/wp-content/uploads/2023/02/1_24140922240.jpg</url><width>443</width><height>600</height></post-thumbnail>	</item>
	</channel>
</rss>
