Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Various site-wide changes can be made using the web-based configuration options available within eMuseum. Once authenticated as an administrator, click the cog icon or toggle the main menu open and click "Configuration" to access the configuration page. The next sections will guide you through all available configuration options.
Skins, or themes, give eMuseum its look, feel, and structure. You can adjust most aspects of your site's appearance by editing its default skin files or by adding and activating a new skin. A skin consists of file types common to the web, such as CSS stylesheets, JavaScript files, image (graphics) files, and eMuseum-specific template files ('.tml').
eMuseum 6 uses modern web standards with a clean separation between content and design, allowing anyone familiar with CSS styles to make basic changes to your site's appearance. eMuseum template files are HTML-compatible and also include processing logic. This logic is unobtrusive to web browsers, which will render the content as HTML.
Adding and activating a skin is straightforward. Your installation package contains 3 skins by default:
Internal - the default design that can be modified through configuration options but should not have its files altered.
default_neue - a copy of the internal skin which can be altered or copied. This is good for small design changes using eMuseum's default design as the basis.
skeleton_neue - A stripped-down/minimalist skin with all features but little design opinion. This is a good starting point for completely new designs.
To create your own skin, you can do so by:
Navigating to \skins
Copy the "defaultSkin" to start with a base exactly like the active internal skin, or copy the "skeleton" skin to start with a base that has all functionality but is stripped down with very little default styling to allow for a complete re-skinning.
Rename the skin you just copied
Refresh the skins configuration page and select the new skin from the "Available Skins" select list.
You can create additional skins by copying and renaming the default Skins directory or creating an empty directory with a unique skin name and copying only selective files (e.g.,' Layout.tml' and 'styles.css') into the Skins directory. eMuseum checks the active Skins folder for an override to the default skin running under the web application container:
If an override is found in the active Skins directory, it will load that template, stylesheet, etc.
If an override is not found in the active Skins directory, then the default template, stylesheet, etc., is used.
This allows you to easily modify and manage a few select files under your Skins directory while deferring to the default set of templates for most of your needs.
Note: There are no restrictions on how you name a skin. The name will only appear on the Skins Configuration page; it is never displayed to the end-user.
The Appearance configuration options provide a comprehensive set of tools to customize the visual aspects and layout of your eMuseum site. These settings allow for the personalization of colors, fonts, layout structures, and navigation behaviors, ensuring the site aligns with your institution's branding and user experience goals. Below is a detailed description of each configuration option, including practical examples of how they could be used:
General Settings
Enables rounded corners for UI elements such as buttons and text inputs. Using rounded corners can create a softer, more modern look for the website.
Transforms menu items and small labels to upper case. Labels for buttons like "SUBMIT" and "CANCEL" appear in all caps for emphasis.
Displays a large search box inside the content area instead of in the header.
Enables social media sharing buttons for objects in the collection, allowing users to share individual works using social media applications such as Facebook, Twitter, and Pinterest, as well as email. It also enables sharing in the List, Images, and Detail pages.
Sets the color for hyperlinks across the site. Choosing a distinct blue for all links to maintain visual consistency.
Sets the color for links when the mouse hovers over them to provide clear visual feedback to users.
Sets the color for menu items and text.
Sets a color for highlighted elements such as buttons, selected text, and active states.
Sets the background color on detail pages when using a one-column layout to ensure images and videos stand out.
Sets the maximum width of the content for all pages.
Sets the font face for text in the body of all pages.
Sets the font face for titles on all pages.
Sets the base font size, which scales all text sizes up or down.
Sets the amount of space between items in grid view.
Adds a colored bar behind the header section.
Adds padding to the top and bottom of the header.
Sets the color of the header bar if it is enabled.
Sets the text color inside the header if the header bar is enabled.
Enable or disable the page footer.
Adds padding to the top and bottom of the footer.
Sets the background color of the footer.
Sets the color of text inside the footer.
Displays filters and results in one column.
Displays the filters and results in two columns.
This page explains the installation procedure for eMuseum.
By default, the following ports will be used:
Tomcat
HTTP: 80
HTTPS: 443
Shutdown: 8005
Solr: 8983
On Windows, we will install everything into a base folder (e. g. C:\eMuseum):
C:\eMuseum
\home
\jdk17
\solr9
\Tomcat9
It is recommended to use the major version in the folder name but leave out any other version part. That will ensure that references do not need to be adjusted on every update.
On Linux, Java will be installed via the package management, Tomcat will be installed manually at /opt/tomcat9 with a working directory at /var/opt/tomcat, Solr will be installed via the official installation script with a symlink at /opt/solr and the data located at /var/solr, and eMuseum will be installed to /var/opt/emuseum:
/opt/tomcat9
/opt/solr → /opt/solr-x.y.z
/var/solr
/var/opt/tomcat
/var/opt/emuseum
Create a base folder, e. g. C:\eMuseum, and extract the installation package into it. Rename the resulting installation folder to home.
Extract the installation package and move it to /var/opt/emuseum:
Next, install all required 3rd-party requirements.
Install Java in the required version.
Install the OpenJDK package in the required version via the package management.
On Ubuntu, this can be done with apt:
Install the required version of Tomcat.
Execute the installer. Un-check all additional options like the documentation and the manager, but select all options under the root item (Tomcat Native and service). The first path the installer asks for is the Java directory, not the Tomcat installation folder. Select C:\eMuseum\jdk17. The second path will be the Tomcat installation folder. Select C:\eMuseum\Tomcat9 (adjust the folder name to match the Tomcat version). Use only “eMuseum” as the name; the installer will add “Apache Tomcat” in front of it. Starting the service to let Tomcat create some default folders is recommended.
After the installation, stop the Tomcat service and increase the memory by executing the Tomcat configuration utility at C:\eMuseum\Tomcat9\bin\eMuseumw.exe. Under the tab “Java,” set the start memory to “512” and the maximum memory to a minimum of “4096”.
Next, adjust the port of the HTTP connector in C:\eMuseum\Tomcat9\conf\server.xml from “8080” to “80” and increase the maxParameterCount to "3000":
To set up HTTPS, uncomment one of the example connectors, change its port to “443” and adjust the TLS settings.
Download and import Tomcat PGP keys:
Download, verify and extract Tomcat 9 tar ball to /opt/ (adjust the version to use the latest):
Create a symlink tomcat9 → apache-tomcat-9.0.84:
Create a Tomcat group and user:
Adjust the file permissions:
Create a working directory for Tomcat:
Next, adjust the port of the HTTP connector in /var/opt/tomcat/server.xml from “8080” to “80” and increase the maxParameterCount to "3000":
To set up HTTPS, uncomment one of the example connectors, change its port to “443” and adjust the TLS settings.
Finally, create a Systemd service unit at /etc/systemd/system/tomcat9.service:
Enable and start the service:
If you want to use a standalone database instance, install one of the supported Database Management Systems. Otherwise, use an existing database server.
If you want to use a standalone instance of Solr, please follow the following steps. If you plan to use a shared instance, skip the next steps.
On the download page, you will only find tar.gz files. However, on a recent version of Windows, the following tar can be used via the command line to extract the package (adjust the filename to match the Solr version):
Configure the JVM that Solr uses by setting the following line in C:\eMuseum\solr9\bin\solr.in.cmd:
Start the service.
Create a new eMuseum database including user as follows.
If you want to use SQL Server Management Studio, open it, connect to the database server, and do the following steps:
Create a new login with the name “emuseum” and a strong password. Disable all password policies.
Create a new database named “emuseum” with the owner set to “emuseum” and the Recovery Model set to “simple”
Alternatively, run the following SQL script (adjust the login password!):
Either use a management client of your choice or run the following SQL script (adjust the login password!):
If the database server is running on a different host, adjust the host value. Use “%” to allow the user to connect from any host.
Since version 6.4, eMuseum creates the database schema automatically on start-up.
Copy eMuseum’s core configuration to Solr’s data folder.
Copy eMuseum’s core configuration from C:\eMuseum\home\solr\solr9 to Solr’s data folder.
If Solr has been installed for eMuseum only, the data folder will be C:\eMuseum\solr9\server\solr.
Copy eMuseum’s core configuration from /var/opt/emuseum/solr/solr9/ to Solr’s data folder.
If Solr has been installed for eMuseum only, the data folder will be /var/solr/data/.
If Solr is not used exclusively for eMuseum, the data folder depends on the Solr setup. Rename the core folders to emuseum_records and emuseum_vocabularies (if you use a shared Solr instance for several eMuseum applications, use a prefix like the client name). Additionally, change the core names inside core.properties files within the core folders to match the folder names.
Create a context descriptor by copying an example context.xml file from C:\eMuseum\home\bin\context to C:\eMuseum\home\bin\ROOT.xml which matches the database management system (e. g. context.mssql.xml for SQL Server).
Create a context descriptor by copying an example context.xml file from /var/opt/emuseum/bin/context/ to /var/opt/emuseum/bin/ROOT.xml which matches the database management system (e. g. context.mssql.xml for SQL Server)
Adjust the following settings:
emuseum.home
The path to the eMuseum folder: C:\eMuseum\home (Windows) or /var/opt/emuseum (Linux)
emuseum.jdbcurl The database connection URL
emuseum.dbuser The database user name
emuseum.dbpassword The database user password
solr.serverUrl The base URL of the Solr server
solr.corePrefix
The prefix of the Solr cores (including any trailing character like _).
Copy the context descriptor to Tomcat.
Copy the XML file from above to Tomcat’s configuration folder: C:\eMuseum\Tomcat9\conf\Catalina\localhost\ROOT.xml
Copy the XML file from above to Tomcat’s configuration folder: /var/opt/tomcat/conf/Catalina/localhost/ROOT.xml
Deploy the war file.
To deploy the webapp on Window, copy the war file from C:\eMuseum\home\bin\emuseum-6.4.war (adjust the version number) to C:\eMuseum\Tomcat9\webapps\ROOT.war.
To deploy the webapp on Linux, copy the war file from /var/opt/emuseum/bin/emuseum-6.4.war (adjust the version number) to /var/opt/tomcat/webapps/ROOT.war.
For Tomcat to match the configuration with the application, it is crucial that the war file and the context description have the same name (except for the file extension).
Start the Tomcat service.
Change the superuser password to a strong password.
Set a license under Configuration → Application → License.
Adjust the following application settings:
Application name
Hostname
Use HTTPS (if enabled and a domain has been set up)
| Masonry | Standard | Fit | Mosaic |
|---|---|---|---|
| One column | Two column | Three column |
|---|---|---|
Acquire an eMuseum installation package as the first step of the installation. Default packages can be downloaded from the .
Download Java from . Make sure to pick the correct version and architecture. Then, install it to C:\eMuseum\jdk17 (adjust the folder name to match the Java version).
Download Tomcat from . For an easy installation that includes a service, pick the 32-bit/64-bit Windows Service Installer.
Download the Solr binary release from and extract the package to C:\eMuseum\solr9 (adjust the folder name to match the Solr version).
To set up Solr as a service, download the latest version of the Windows Service Wrapper (WinSW) from (pick the Windows 64-bit executable). Move the file to C:\eMuseum\home\utils\WinSW and rename it to eMuseumSolr.exe. Next, rename the XML file eMuseumSolr.example.xml in that folder to eMuseumSolr.xml (both the XML and the exe files have to have the same name). Finally, open a command prompt with administrator permissions, navigate to the folder, and run the following command:
Download Solr binary release from and follow the .
Restart Solr for the changes to take effect. Optionally, you can log in to the Solr admin dashboard at and check if the two cores are listed.
Open a web browser and navigate to . Login as superuser/superuser.
The Logo Configuration page allows you to assign a logo to appear in the top banner of all pages on your eMuseum site. The logo configured here will not display on non-configuration pages in the Skeleton skin (or copies).
This page documents the manual steps required to upgrade an existing eMuseum installation.
Before applying changes specific to eMuseum 6. found in the sections below, all changes required to upgrade earlier versions of 6.0, 6.1, 6.2 and 6.3 must be applied. Those changes can be found in the corresponding release notes.
In addition to Java 11, Java 17 is now supported
In addition to Solr 8, Solr 9 is now supported
Database changes are now handled by the application at startup. No manual steps are required.
If the data folder within the eMuseum home directory is used (<EMUSEUM_HOME>/solr/), adjust the Solr configuration to point to <EMUSEUM_HOME>/solr/solr8 for Solr 8 or to <EMUSEUM_HOME>/solr/solr8 for Solr 9.
If a separate Solr data folder is used (instead of <EMUSEUM_HOME>/solr/), copy over the files from <EMUSEUM_HOME>/solr/solr8 for Solr8 or from <EMUSEUM_HOME>/solr/solr9 for Solr 9.
Template updates are only required for custom skins.
For each custom skin (sub-folders in the <EMUSEUM_HOME>/skins/ folder), apply the following changes. Please note that custom skins only contain files for custom changes. If a mentioned file does not exist in the custom skin’s folder, no changes need to be done.
Merge changes on the following template files (if present):
If a separate Solr data folder is used (instead of <EMUSEUM_HOME>/solr/solr8) for Solr 8, copy over the following files:
<EMUSEUM_HOME>/solr/solr8/records/conf/solrconfig.xml
<EMUSEUM_HOME>/solr/solr8/vocabularies/conf/solrconfig.xml
If a separate Solr data folder is used (instead of <EMUSEUM_HOME>/solr/solrX), copy over the following files (adjust X to your Solr version):
<EMUSEUM_HOME>/solr/solrX/records/conf/solrconfig.xml
<EMUSEUM_HOME>/solr/solrX/vocabularies/conf/solrconfig.xml
Template updates are only required for custom skins.
For each custom skin (sub-folders in the <EMUSEUM_HOME>/skins/ folder), merge changes on the following template files (if present):
com/gallerysystems/emuseum/core/components/admin/MemoryWidget.tml
com/gallerysystems/emuseum/core/components/pageviews/objects/Detail.tml
com/gallerysystems/emuseum/core/components/profile/AddCustomFieldConfigModal.tml
com/gallerysystems/emuseum/core/components/profile/SimilarFieldConfig.tml
com/gallerysystems/emuseum/core/pages/admin/nodes/NodesIndex.tml
Template updates are only required for custom skins.
For each custom skin (sub-folders in the <EMUSEUM_HOME>/skins/ folder), merge changes on the following template files (if present):
com/gallerysystems/emuseum/core/components/DetailActions.tml
com/gallerysystems/emuseum/core/components/IIIFLink.tml
com/gallerysystems/emuseum/core/components/Layout.tml
com/gallerysystems/emuseum/core/components/favorites/FavoritesBar.tml
Template updates are only required for custom skins.
For each custom skin (sub-folders in the <EMUSEUM_HOME>/skins/ folder), merge changes on the following template files (if present):
com/gallerysystems/emuseum/core/pages/advancedsearch/AdvancedsearchResults.tml
com/gallerysystems/emuseum/core/pages/search/SearchResults.tml
If a separate Solr data folder is used (instead of <EMUSEUM_HOME>/solr/solr8) for Solr 8, copy over the following files:
<EMUSEUM_HOME>/solr/solr8/records/conf/solrconfig.xml
<EMUSEUM_HOME>/solr/solr8/vocabularies/conf/solrconfig.xml
Template updates are only required for custom skins.
For each custom skin (sub-folders in the <EMUSEUM_HOME>/skins/ folder), merge changes on the following template files (if present):
com/gallerysystems/emuseum/core/base/view/page/AbstractViewPage.tml
com/gallerysystems/emuseum/core/components/pageviews/events/Detail.tml
com/gallerysystems/emuseum/core/components/pageviews/media/Detail.tml
com/gallerysystems/emuseum/core/components/profile/QuickSearchFieldConfig.tml
com/gallerysystems/emuseum/core/pages/advancedsearch/AdvancedsearchResults.tml
com/gallerysystems/emuseum/core/pages/search/SearchResults.tml
com/gallerysystems/emuseum/core/pages/users/UsersIndex.tml
If a separate Solr data folder is used (instead of <EMUSEUM_HOME>/solr/solrX), copy over the following files (adjust X to your Solr version):
<EMUSEUM_HOME>/solr/solrX/records/conf/schema.xml
<EMUSEUM_HOME>/solr/solrX/records/conf/solrconfig.xml
<EMUSEUM_HOME>/solr/solrX/vocabularies/conf/schema.xml
<EMUSEUM_HOME>/solr/solrX/vocabularies/conf/solrconfig.xml
If a custom Profile for the People module exists (file <EMUSEUM_HOME>/profiles/people.xml), locate the field “letter” and change its attribute “type” to “keyword”:
<field id="letter" type="keyword">
Run a full indexing after the changes above.
Template updates are only required for custom skins.
For each custom skin (sub-folders in the <EMUSEUM_HOME>/skins/ folder), merge changes on the following template files (if present):
com/gallerysystems/emuseum/core/components/pageviews/people/Detail.tml
If a separate Solr data folder is used (instead of <EMUSEUM_HOME>/solr/solrX), copy over the following files (adjust X to your Solr version):
<EMUSEUM_HOME>/solr/solrX/records/conf/schema.xml
<EMUSEUM_HOME>/solr/solrX/records/conf/solrconfig.xml
<EMUSEUM_HOME>/solr/solrX/vocabularies/conf/schema.xml
<EMUSEUM_HOME>/solr/solrX/vocabularies/conf/solrconfig.xml
Template updates are only required for custom skins.
For each custom skin (sub-folders in the <EMUSEUM_HOME>/skins/ folder), merge changes on the following template files (if present):
com/gallerysystems/emuseum/core/components/media/viewers/DocumentViewer.tml
Navigate to Configuration → Data and Search Settings → Field Configuration, select the Objects module, open Search → Quick Search, click on the cog wheel of the “invno” field and uncheck the Search Suggestions option “tokenized”.
Run a full indexing after making these changes.
Template updates are only required for custom skins.
For each custom skin (sub-folders in the <EMUSEUM_HOME>/skins/ folder), merge changes on the following template files (if present):
com/gallerysystems/emuseum/core/components/DetailsBlock.tml
If a separate Solr data folder is used (instead of <EMUSEUM_HOME>/solr/solr9) for Solr 9, copy over the following files:
<EMUSEUM_HOME>/solr/solr9/records/conf/schema.xml
If a custom Profile for the People module exists (file <EMUSEUM_HOME>/profiles/people.xml), change the label of the field “alphaSort” to “Alpha Sort”.
This page documents all notable changes to eMuseum.
Gracefully handle custom fields modal if the user logged out on another screen
Fix Thesaurus terms on multiviews
Show the Favorite delete icon on the list and table view
Fix Favorites records to not disappear after changed data import
Hide the Favorites icon if Favorites are restricted
Fix report for large dataset not crashing application
Add new database indexes for linked tables
Do not link values from filterable fields when a standard license is applied
Do not expose media request values in the media request error page
Close all prepared statements during the import
Fix the Restricted Bots filter to throw an NPE if the User-Agent is empty
Update Tapestry to version 5.8.6
Modify sitemap projection query to respect record role restrictions
Fix multi-value fields to include all values on multi-views
Do not use phrases in Advanced Search queries for nested fields
Close all asset streams
Do not load non-image media into reports
Fix report field configuration to index new fields
Always set both “width” and “height” in IIIF Image API image sizes
Include the full image size in IIIF Image API info
Fix “on” canvas URI in IIIF Image info
Record node in indexing history when indexing media or vocabulary fields
Improve the default label for “alphaSort” field in the People module
Do not use a stop words filter for keyword fields on Solr 9
Handle combination of thesaurus and date range filter
Properly encode thesaurus filter values for results API links
Fix the Labels configuration page when the default language is not English
Fix JSON API for advanced search results when the language is explicitly set via the URL
Allow Advanced Search multi-select blank option label customizations
Fix image derivatives after disabling "pad to square"
Fix duplicated results when returning to the results page for Infinite Scrolling
Honor "page" parameter for result sets if Infinite Scrolling is enabled
Overwrite default labels for result views for secondary languages
Prevent report generation for disabled reports
Fix the Output Markup option for the Object “titles” field
Address default invno field suggestions settings
Fix deletion of custom fields, not leaving API references behind
Fix Bootstrap JavaScript includes
Update Tapestry to version 5.8.3
Fix Thesaurus Solr processor count for type-filtered fields
Include Loans and Events without media in Sitemap.xml
Delete Network API package if extracting data fails
Fix search within Thesaurus tree
Fix JSON API for search results when the language is explicitly set via the URL
Trigger re-index on media import
Add mimetype as "type" attribute to embedded documents
Fix the initial state of DisableByRadio mixin
Fix date filter display for Virtual Groups based on dates
Support Thesaurus terms for search suggestions
Use minimal tokenization/filtering for search suggestions
Run Solr processor for cross-module relationships on all modules
Use W3C datetime format for Sitemap.xml
Fix display of people display names with HTML characters
Fix field label overwrites for multiple languages
Move Solr 9 auto-commit settings to update the handler
Use URL Service for encoding Collection parameter
Do not use Solr stop words filter for keyword fields
Fix record count for multi-view reports
Fix long loading times for multi-select lists
Update sitemap media links to use URL service with primary media node and source ID values
Load robots.txt when the site runs in production mode
Use list for “profile” property in IIIF Image API’s image information response
Fix image mirroring
Handle Thesaurus concepts without descriptors in the filter panel gracefully
Rename the WinSW example file for Solr service to avoid overwriting
Prevent users from entering negative quick search boost values
Fix the display of the Thesaurus term on the Event and Media details page
Prevent unrestricted access to Favorites of other users via reports
Prevent unrestricted access to some configuration pages
Prevent Stored XSS in usernames
Prevent anonymous users from creating Virtual Groups and Favorites
Do not expose the full file path in the image upload error message
Prevent unrestricted access to restricted records via reports
Add GitLab pipeline job to deploy customization projects automatically
Make Advanced Search errors in results views visible to the user
Handle fields without "name" attribute for People letters gracefully
Fix indexing progress for joining fields with multiple values
Fix the typo in the Exhibitions index page route
Fix indexing progress for join fields without purpose
Support custom media dispatchers for link generation
Render Unicode characters in reports properly
Respect role restrictions on records in relation to related module views
Add missing value for "events.vocindexingevent-label" to message catalogue
Fix user media files to fallback to regular media files for Network API version 1.1
Transform images if user media is enabled
Do not link Thesaurus attributes on standard license level
Fix parameter encoding when switching language
Fix "nullable" for several entity attributes
Fix URL encoding of context path parameters
Fix the error when navigating to a person from the People/Index page after scrolling
Do not call "optimize" after Solr indexing
Fix searching related records
Move Solr auto-commit settings to update the handler
Set default omit generator meta config value in internal web.xml
Do not hardcode per-page value when infinite scrolling is enabled
Index only report fields that are for multi-view reports
Fix custom fields to show up in detail reports
Pass module name to search result pages correctly
Hide empty labels in reports
Fix HTTP cache headers for Custom CSS file
Do not log warnings for single-value fields without nested values on detail pages
Update JSass to version 5.10.5
Fix user media files to fallback to regular media files
Fix display of TDB thesaurus-based term values in reports
Limit in-memory caches by entry count instead of memory size
Fix the position of modal close button
Fix exceptions for fields with multiple values in multiview reports
Fix default language for custom UI literals file
Fix the message catalogue in the Thesaurus and select model
Fix the comparison of fields without labels on media configuration page
Handle duplicated section keys in the message catalogue
Fix "colud" typo in the "sort field not found" message
Fix the favorites toolbar delete check to show correctly
Only allow the currently logged-in user or admins to download a user's data in CSV
Gracefully handle invalid Thesaurus concept URIs for filters etc.
Fix IIIF icon display and add icon alt text
Fix list/list item markup surrounding the language switcher in the footer
Revert changes on db create scripts
Use Solr auto commits to avoid large transaction logs
Clean-up generated reports
Fix module intro text editor
Handle Thesaurus concepts without a descriptor
Show blank option for type-filtered field values
Sort type-filter values by Unicode rules
Make data role import by name case-insensitive
Fix migration of primary key for collections_objects table
Fix field “mediaExistence” on detail pages
Delete Network API package if chunk transfer is aborted
Fix ImageViewer padding-bottom on Category Group pages
Fix severity for Group edit configuration error message
Fix Discover More fields not being configurable
Fix Person Object images logic to use only non-null media entries
Fix scheduled job to clean import/indexing history
Use count query to check relationship existence
Show memory values on the admin dashboard in Megabytes
Sort Nodes on the Nodes index page alphabetically by default
Fix saving an empty Restricted Words List
Do not set the HTTP header "Connection" for stream responses
Do not call “optimize” after Solr indexing
Disable Solr “infoStream” option
Fix CSS class conflict when configuring the Name field as a filter option
Set session timeout in web.xml
Fix image loading icon to disappear for Infinite Scrolling on non-Masonry layouts
Re-enable building Solr suggesters
Limit file transformation cache by entry count instead of memory size
Fix overlapping images for files with width and height not being set
Preserve many2many relationship references on upgrade
Support Solr via HTTPS
Fix thumbnails on the Groups List configuration page
Fix Favorites being indexed by a full indexing
Create config option for image alt text
Make Solr core names configurable
Add IIIF Presentation Collection for result sets
Add option/action to clean import/indexing history
Add detail and multiview API field configuration
Limit media processing to a small number of threads
Update RESTEasy to version 5
Add profile configuration for IIIF metadata fields
Use Apache Commons Bean Utils to access properties
Use static URIs in mapping
Add an option to disable Relevance sort per module
Provide field configuration for selectable Advanced Search field values
Use GitLab’s Maven repository
Show multiview tiles on page load and re-layout after each image has been loaded
Set aspect ratio for images on multiviews
Update Tapestry to version 5.7
Replace JAXB with Java classes for Config and Profiles
Show the git version description on the admin dashboard
Use persistent URLs for IIIF resources
Upgrade Gradle Wrapper to version 7
Output multi-value fields correctly in IIIF Presentation API
Reorganize field configuration loop groupings
Add an option for preventing crawling of the entire site
Stream writing of RDF data
Replace Apache Jena with Eclipse RDF4J
Report Thesaurus import progress
Support automatic database schema migration
Use the FieldLabel component for rendering the Object Detail on the view label
Use the "Preserve Linebreaks" option for the dimensions field by default
Omit Tapestry generator metatag
Update Hikari to version 5
Use single-column primary key for many2many relationship tables
Flip Virtual Group name and URL fields
Add generic TML overrides for custom-filtered fields
Get image dimensions from the file header
Do not compare CSRF tokens for new and expired sessions
Update SpotBugs Gradle plugin to version 5
Update Spring Data to version 2.6
Update Spring Security to version 5.6
Update Hibernate to version 5.6
Update Apache Commons IO to version 2.11
Update Jackson Databind to version 2.13
Update Solr and Lucene to version 8.11
Update Bouncy Castle to version 1.70
Update JSONjava to version 20211205
Update Apache Tika to version 2
Update Handlebars to version 4.3
Update OpenCSV to version 5.6
Update Javassist to version 3.28
Update Microsoft JDBC to version 10
Update jQuery UI to version 1.13
Update video.js to version 7.18
Preserve external vocabulary data during data import
Do not use a single transaction for importing data from external vocabularies
Index fields for external vocabularies after import
Reduce expiry for "file transformation" cache
Increase database connection pool settings
Move metadata options to the application configuration page
Show all available modules on the field configuration page
Index module after enabling it
Validate field mapping for complex attributes
Replace getScaledInstance() for resizing images
Expose metrics in OpenMetrics format
Operate Solr as a system service
Remove Solr JMX configuration
Update Tapestry to version 5.8
Update saved search queries for Groups based on Favorites
Support TIFF image format by IIIF Image API
Remove the TMS Table/Field column from the field configuration
Let Solr processor decide if to run
Remove Profile field attribute “iterate”
Add potential re-index warning to the field configuration page
Split Liquibase changelog for EM-3174
Pass root entity to Network API mapping source methods
Close Networkapi transfer client
Use separate Liquibase changelog files for custom schema updates
Avoid Tapestry warnings about jQuery UI images
Add handling for custom thesconcepts in the Advanced Search
Hide Advanced Search “select list” for non-text fields
Place "CharsetFilter" filter after "StoreIntoGlobals" filter
Update RDF4J to version 4
Increase Solr memory requirements
Resolve Thesaurus concept URIs on multiviews
Hide Node name in type-filtered field types for singe-Node instances
Cache component class resolution
Use parallel streams for Profile lookups
Update Gradle Wrapper to version 7.4
Update JSON library to version 20220320
Update Apache Tika to version 2.4
Update Solr and Lucene to version 9
Update .gitignore to account for the new solr directory structure
Group type-filter values by their label
Automatically migrate Profile changes
Indicate deleted type-filter values in the field config
Support Java 17
Index API result fields
Fix the clipboard copy function
Fix creating custom flex fields without associated group
Use label overrides in the API output
Fix schema generation to be compatible with the Jena version
Fix thesaurustermspath fieldId reference
Fix the display of custom thesaurus field values in the filter panel
Fix Liquibase changelog for EM-2829
Fix custom thesaurus fields searchable without “thesconcepts” field being searchable
Fix literals that inherit other literals from appearing as being overridden
Fix Alternative Text Ellipsis description typo
Fix adding/removing fields to/from Reports
Set the correct number of media processing threads at startup
Fix validation of type-filtered field modal
Handle Thesaurus values without language gracefully
Close Solr client on application shutdown
Update enabled modules after applying a new license
Fix field configuration to add multiview fields to Profile Mapping
Fix deleting of field mapping
Allow Advanced Search select list option for "keyword" fields
Fix error when creating a type-filtered Flex Field without a group
Fix Thesaurus tree count if the "use select list" option is enabled
Handle new elements for existing configuration
Add UI to manage translation literals/properties
Allow admins to create new fields based on sub-queries of existing fields
Stacks images on top of each other like bricks.
Each item is given an equal amount of space on the grid.
Crops images so that images are a uniform size.
Crops images with varied sizing throughout the grid.
