<?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>Monthly meetup | museum-digital: blog</title>
	<atom:link href="https://blog.museum-digital.org/tag/monthly-meetup/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>Sat, 18 Mar 2023 23:17:51 +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>Monthly meetup | 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>A Calendar is a Commitment</title>
		<link>https://blog.museum-digital.org/2023/03/14/a-calendar-is-a-commitment/</link>
					<comments>https://blog.museum-digital.org/2023/03/14/a-calendar-is-a-commitment/#respond</comments>
		
		<dc:creator><![CDATA[Joshua Ramon Enslin]]></dc:creator>
		<pubDate>Tue, 14 Mar 2023 00:39:54 +0000</pubDate>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Infrastructure]]></category>
		<category><![CDATA[Project page www.museum-digital.de]]></category>
		<category><![CDATA[Monthly meetup]]></category>
		<category><![CDATA[New Features]]></category>
		<guid isPermaLink="false">https://blog.museum-digital.org/?p=3652</guid>

					<description><![CDATA[Last year, we started a monthly user meet-up. As things go, we managed to continue the series at a stable time slot for some months &#8211; and then we did not anymore. People&#8217;s calendars are of course an issue, but another major one was simply that there were no consistently pre-determined meeting URLs. Over the <a href="https://blog.museum-digital.org/2023/03/14/a-calendar-is-a-commitment/" class="more-link">...</a>]]></description>
										<content:encoded><![CDATA[
<p>Last year, we started a <a href="https://blog.museum-digital.org/tag/monthly-meetup/">monthly user meet-up</a>. As things go, we managed to continue the series at a stable time slot for some months &#8211; and then we did not anymore. People&#8217;s calendars are of course an issue, but another major one was simply that there were no consistently pre-determined meeting URLs.</p>



<p>Over the weekend, we have added a new feature to the project page, <a href="http://www.museum-digital.org">www.museum-digital.org</a>: a calendar for trainings, meetings, and the like. The events for this calendar are pulled from various shared calendars via the respective iCalendar files and compiled into lists of the upcoming events.</p>



<p>While the primary source for events thus far is the <a href="https://verein.museum-digital.de/events/">calendar compiled by the German association</a> for museum-digital, the <a href="https://verein.museum-digital.de/">museum-digital e.V.</a>, it also includes events in English. We can thus schedule the meetings ahead of time with meeting URLs set ahead of time without having to write a blog post every time. On the other hand, (publicly) scheduled events will be kept for sure.</p>



<p>And thus, publishing the calendar also means that this time around, we will surely do better and continue the series of monthly user meet-ups on every Tuesday of a month, 5 to 7 p.m. consistently for longer than we did last year.</p>



<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>
					
					<wfw:commentRss>https://blog.museum-digital.org/2023/03/14/a-calendar-is-a-commitment/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-thumbnail><url>https://blog.museum-digital.org/wp-content/uploads/2023/03/about-md-org-calendar-en.webp</url><width>600</width><height>321</height></post-thumbnail>	</item>
		<item>
		<title>Monthly museum-digital user meetup (September 2022) / New Features</title>
		<link>https://blog.museum-digital.org/2022/09/23/monthly-museum-digital-user-meetup-september-2022-new-features/</link>
		
		<dc:creator><![CDATA[Joshua Ramon Enslin]]></dc:creator>
		<pubDate>Fri, 23 Sep 2022 13:01:07 +0000</pubDate>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[Frontend]]></category>
		<category><![CDATA[Importer]]></category>
		<category><![CDATA[musdb]]></category>
		<category><![CDATA[Monthly meetup]]></category>
		<category><![CDATA[New Features]]></category>
		<category><![CDATA[Object search (musdb)]]></category>
		<guid isPermaLink="false">https://blog.museum-digital.org/?p=3377</guid>

					<description><![CDATA[On September 6th 2022, we continued our monthly user meetups. As should best become the norm, we discussed recent new features of the preceeding month and plan a next meetup on the first Tuesday of October (October 4th, 2022, 5 p.m. at https://meet.jit.si/museum-digital-meetup-202210). A summary of the new features and updates can be found in <a href="https://blog.museum-digital.org/2022/09/23/monthly-museum-digital-user-meetup-september-2022-new-features/" class="more-link">...</a>]]></description>
										<content:encoded><![CDATA[
<p>On September 6th 2022, we continued our monthly user meetups. As should best become the norm, we discussed recent new features of the preceeding month and plan a next meetup on the first Tuesday of October (October 4th, 2022, 5 p.m. at <a href="https://meet.jit.si/museum-digital-meetup-202210">https://meet.jit.si/museum-digital-meetup-202210</a>).</p>



<p>A summary of the new features and updates can be found in the following.</p>



<h2 class="wp-block-heading">Recent Updates and New Features</h2>



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



<h4 class="wp-block-heading">Support for Imperial Measurement Units for Separated Measurements</h4>



<p>Thus far, musdb only supported metric units for length, width, diameter, etc. It is now also possible to enter measurements in inches and feet. For searching objects smaller or larger than a given number, the number is still expected to be provided in millimeters.</p>



<h4 class="wp-block-heading">Reworked Institution-Wide Settings Page</h4>



<p>Certainly the main focus of our work on improving musdb has been a rather extensive overhaul of the institution-wide settings page. This page is available for users of the user role &#8220;museum director&#8221; and can be reached through the academy-icon in the navigation.</p>



<p>With the batch of updates, the page gets a new design with an always visible table of contents and rather extensive descriptions of each of the available settings. We removed some outdated and confusing options while adding new ones for the newly added <a href="https://blog.museum-digital.org/2022/08/25/strict-modes/">strict modes</a> and inventory number suggestions.</p>



<h4 class="wp-block-heading">Suggestions for Inventory Numbers for New Objects</h4>



<p>On the institution-wide settings page, it is now possible to set a scheme for how the museum forms its inventory numbers. Variable parts are expressed using placeholders:</p>



<ul class="wp-block-list">
<li><code>{no} </code>for a number counting up. For a counter padded to a given number of digits, a number may be added after the place holder (e.g. <code>{no}6</code> for a 6 digit counter in the inventory number.</li>



<li><code>{c_sig} </code>for a signature of the collection</li>



<li><kbd><code>{year}</code></kbd> for the ongoing calendar year).</li>
</ul>



<p>If a regular inventory number in the house is, say, &#8220;2022-000025&#8221;, the scheme would thus be <code>{year}-{no}6</code>.</p>



<p>If an inventory number scheme has been set, an additional suggestion button will appear in front of the entry field for inventory numbers on the page for adding new objects.</p>



<h4 class="wp-block-heading">Searching for Objects by Their Entry Dates</h4>



<p>Similar to how secondary search indexes for measurements greater or smaller than a given value have existed for some time, entry dates, estimation dates, etc. are now made properly searchable through the object search in musdb. For this, dates need to be set in a coherent, maschine-readable form that is greatly aided by the new strict modes.</p>



<h4 class="wp-block-heading">Strict Modes</h4>



<p>See the <a href="https://blog.museum-digital.org/2022/08/25/strict-modes/">dedicated blog post</a> on this topic.</p>



<h4 class="wp-block-heading">Deletion Buttons in the Toolbar of Entry Pages</h4>



<p>If one wanted to delete an object group, one thus far needed to find the object group in the object group overview and delete it from there. There was no option to delete it right from the page of the object group itself.</p>



<p>For a more straight-forward control, we now added deletion buttons on the editing pages of object groups, exhibitions, etc. These deletion buttons can be found in the toolbar on the right of the screen.</p>



<h4 class="wp-block-heading">PNG Supported When Uploading Object Images</h4>



<p>Since object images are almost always photos or scans that feature a multitude of colors and few solid blocks of color, JPG is a much better format than PNG for storing (compressed) object images. musdb hence only accepted JPG images for uploads thus far. Since some museums however have internal rules for keeping their object images&#8217; working copies in PNG, we now allow PNG uploads and then convert the PNG images to JPG during the upload process.</p>



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



<h4 class="wp-block-heading">License Descriptions Consistently Displayed on Object Pages</h4>



<p>Until last month, a description of the metadata license of an object page (to be found at the bottom of the page) was only available for the license CC BY-NC-SA. We now removed the exception and made descriptions and links to the license text available for all available licenses.</p>



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



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



<li>Further modularize parsers</li>



<li>Added new parsers for EasyDB (work in progress)</li>



<li>Allow importing images by their URLs to locally hosted ones</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>
					
		
		
			</item>
		<item>
		<title>Monthly museum-digital user meetup (August 2022) / New features</title>
		<link>https://blog.museum-digital.org/2022/08/16/monthly-museum-digital-user-meetup-august-2022-new-features/</link>
		
		<dc:creator><![CDATA[Joshua Ramon Enslin]]></dc:creator>
		<pubDate>Tue, 16 Aug 2022 12:45:11 +0000</pubDate>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[Frontend]]></category>
		<category><![CDATA[Importer]]></category>
		<category><![CDATA[musdb]]></category>
		<category><![CDATA[Project page www.museum-digital.org]]></category>
		<category><![CDATA["Objects on map"]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[Map views]]></category>
		<category><![CDATA[Monthly meetup]]></category>
		<category><![CDATA[New Features]]></category>
		<category><![CDATA[Object search (musdb)]]></category>
		<category><![CDATA[Object selection (musdb)]]></category>
		<guid isPermaLink="false">https://blog.museum-digital.org/?p=3351</guid>

					<description><![CDATA[On Tuesday last week we had our first international user meetup. As proposed, we mainly discussed recent updates and new features before opening up the general discussion. In the process, we also wrote a list of the new features introduced with short notes on each. You can find it below. The next monthly meetup is <a href="https://blog.museum-digital.org/2022/08/16/monthly-museum-digital-user-meetup-august-2022-new-features/" class="more-link">...</a>]]></description>
										<content:encoded><![CDATA[
<p>On Tuesday last week we had our first international user meetup. As proposed, we mainly discussed recent updates and new features before opening up the general discussion. In the process, we also wrote a list of the new features introduced with short notes on each. You can find it below.</p>



<p>The next monthly meetup is scheduled for Tuesday, September 6th 2022, 5 p.m. (this post will be updated with a link to the meeting about a week before the meeting, as we are currently trying to organize a meeting room at Zoom or a similar service).</p>



<p><strong>Update</strong>: The meeting will take place at https://meet.jit.si/museum-digital-meetup-202209</p>



<span id="more-3351"></span>



<h2 class="wp-block-heading">Recent Updates and New Features</h2>



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



<h4 class="wp-block-heading">XML Export</h4>



<p>Creating new export formats for XML exports (beyond the main export formats md:xml and LIDO 1.0) is now possible using XSL files stored in a new git sub-repository. This git sub-repository is open source. As registration on our main Gitea instance is however restricted, please send a mail before contributing.</p>



<p>In line with this, we have also improved the representation of uncertainty in our default LIDO 1.0 exports. As version 1.1 of the LIDO standard has been recently released, we have also begun working on a LIDO 1.1 export.</p>



<p>Note: The pre-generated exports available through the &#8220;quick export&#8221; option are and will still only generated for LIDO 1.0 and md:xml.</p>



<h4 class="wp-block-heading">Required coordinates when adding new museums</h4>



<p>This update is only relevant to regional administrators. Coordinates of the institution are now required for adding new institutions.</p>



<h4 class="wp-block-heading">QR Codes</h4>



<p>QR codes can now also be exported in <a href="https://en.wikipedia.org/wiki/Scalable_Vector_Graphics">SVG</a> and <a href="https://en.wikipedia.org/wiki/Encapsulated_PostScript">EPS</a>, the two primary vector graphics format for use on the web and professional print layouting.</p>



<p>Another important improvement on QR codes is a new page that simply lists all QR codes leading to the object editing pages of a given search result in musdb. This page offers the option to manually set the size of the QR codes, so that suitable QR codes for internal collection and location management can be printed in bulk in a less paper-consuming way.</p>



<h4 class="wp-block-heading">Calendar</h4>



<p>A calendar view for all the events in the museum (events, start and end of an exhibition, start and end of loans) is now available. It can be reached by hovering the mouse over the puzzle symbol in the navigation. On the calendar page, single calendars can be selected or deselected and one subscribed to using one&#8217;s external calendar programm (e.g. Outlook, Thunderbird, or a mobile phone&#8217;s calendar).</p>



<p>The calendar, and especially the possibility to subscribe to the calendars, is also a first step towards enabling users to set reminders on object pages as this makes much more sense if the reminders can be integrated with one&#8217;s regular calendar application.</p>



<p>The calendar view is built using <a href="https://ui.toast.com/tui-calendar">TUI calendar</a>.</p>



<h4 class="wp-block-heading">Institution-wide Settings and Adding Objects</h4>



<p>The page for institution-wide settings has been re-designed to make it easier navigatable. The table of contents is now always visible, and the section &#8220;links to the institution elsewhere on the web&#8221; has been moved to the institution page.</p>



<p>There however are also some new options on the page. On the one hand, users can now enable or disable the image categorization when uploading images directly when adding new objects (the image recognition is render blocking and often hurts performance more than it actually benefits the inventorization). On the other, it is now possible to add additional fields to be directly accessible upon adding new objects and to make these required. It thus, for example, becomes possible to require a location to be provided before it can be recorded in the system altogether.</p>



<h4 class="wp-block-heading">Watch list</h4>



<p>The watch list feature has been completely re-implemented. The watch list is now generated completely in the browser using easily cache-able data retrieved from APIs. This, first of all, makes the watch list much faster to load and much less of a burden on the server side.</p>



<p>But the new watch list also comes with some new features:</p>



<ul class="wp-block-list">
<li>Users can now have multiple watch lists on the server</li>



<li>Users can share their currently active watch list with other users of the same museum</li>



<li>It is now possible to search objects by a watch list (or transfer the watch list into a search result). Thus, all batch editing and export functions available for object search results are now also available for watch lists. Obviously, this also allows for the watch list&#8217;s objects to be filtered by their place, collection, etc.</li>



<li>Objects can now be added to the watch list in bulk.</li>
</ul>



<h4 class="wp-block-heading">Object search</h4>



<p>The map view of object search results now updates the URL with positions and zoom factor when one browses the map. One can thus share a link to the exact same position one is currently viewing to one&#8217;s colleagues.</p>



<h4 class="wp-block-heading">API</h4>



<p>The API can now be used to delete objects.</p>



<h4 class="wp-block-heading">Design</h4>



<p>Error messages are now visible for four seconds as opposed to the regular 2.4 seconds other feedback messages on inputs are visible.</p>



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



<p>Similar to the referencable maps of object search results in musdb, &#8220;objects on a map&#8221; maps in the frontend <a href="https://blog.museum-digital.org/2022/07/22/referencable-maps-in-the-frontend-and-in-musdb/">are now also referencable</a>. We have also added a legend of event types on the same map.</p>



<h3 class="wp-block-heading"><a href="http://museum-digital.org">museum-digital.org</a></h3>



<p><a href="http://museum-digital.org">museum-digital.org</a>, the general website introducing museum-digital, has been reworked on a new technical basis. It is now statically generated once a day, reducing server costs and increasing performance. There are also many new texts, some new features (such as FAQs) and banner pictures that make the page more attractive.</p>



<p>The contents of the page are licensed under CC BY 4.0 International and can be edited on GitHub (See the repositories for the <a href="https://github.com/museum-digital/museum-digital.org-en">English version</a> of the site and the <a href="https://github.com/museum-digital/museum-digital.org-de">German version</a>).</p>



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



<p>The parser for importing images by their file names now offers a setting option to mark a certain part of a file name as an indicator to import the given image file as a hidden / non-public image.</p>



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



<p>Image: <a href="https://www.jpl.nasa.gov/galleries/visions-of-the-future">Courtesy NASA/JPL-Caltech</a>.</p>



<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/2022/08/55-cancri-e_cut.jpg</url><width>539</width><height>600</height></post-thumbnail>	</item>
		<item>
		<title>Starting a monthly user meet-up for museum-digital</title>
		<link>https://blog.museum-digital.org/2022/08/04/starting-a-monthly-user-meet-up-for-museum-digital/</link>
					<comments>https://blog.museum-digital.org/2022/08/04/starting-a-monthly-user-meet-up-for-museum-digital/#respond</comments>
		
		<dc:creator><![CDATA[Joshua Ramon Enslin]]></dc:creator>
		<pubDate>Wed, 03 Aug 2022 22:36:20 +0000</pubDate>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Monthly meetup]]></category>
		<category><![CDATA[Videoconference]]></category>
		<guid isPermaLink="false">https://blog.museum-digital.org/?p=3343</guid>

					<description><![CDATA[Starting next Tuesday (August 9th), we are planning to do monthly user meet-ups for museum-digital&#8217;s users and administrators to learn about the most recent updates and new features; to have a (public) forum for everybody to ask their questions to members of the core development team and each other and hopefully to extend the discussion <a href="https://blog.museum-digital.org/2022/08/04/starting-a-monthly-user-meet-up-for-museum-digital/" class="more-link">...</a>]]></description>
										<content:encoded><![CDATA[
<p>Starting next Tuesday (August 9th), we are planning to do monthly user meet-ups for museum-digital&#8217;s users and administrators to learn about the most recent updates and new features; to have a (public) forum for everybody to ask their questions to members of the core development team and each other and hopefully to extend the discussion among the community beyond institutional, regional or national borders.</p>



<p>The meetings will take place next week on Tuesday, and following that on every first Tuesday of a month, at 5 p.m. and are open to anybody interested in museum-digital. Generally, we will have a very rough agenda, where we will first discuss the updates and new features of the last month in museum-digital&#8217;s tools and then open up the meeting for general discussion and questions and answers. A short summary of the most recent features will be published here on the blog.</p>



<p>The first meeting will take place on Tuesday, August 9th, 2022, at <a rel="noreferrer noopener" href="https://meet.jit.si/museum-digital-meetup-202208" target="_blank">https://meet.jit.si/museum-digital-meetup-202208</a>. </p>



<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>
					
					<wfw:commentRss>https://blog.museum-digital.org/2022/08/04/starting-a-monthly-user-meet-up-for-museum-digital/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
