The Email Parameters and Event Logging configuration settings allow you to configure eMuseum to work with your SMTP email server. When Email is configured, eMuseum will use the information to send password reminder emails to registered users upon request (and may also send administrator-level messages to the configured administrator address on certain application events).
Enter your default "From" email address here. This address will be displayed to the user receiving emails from eMuseum, and is typically be an address that users should not reply to (e.g., no-reply@ourcollections.org).
Enter the correct Port number here. The default SMTP port number is usually 587, but your SMTP server may require a different port. The port number also depends on the security setting (see below). Please confirm the correct port number with your network administrator.
Enter the user name and password that will be used to authenticate to the SMTP server if your server does not allow anonymous delivery.
By default, eMuseum uses "localhost" as the name for the SMTP server. If this is not a valid name for your SMTP server, enter the appropriate name, along with a valid user account login and password. The SMTP server IP address may also be used.
Select the security option that is supported by the SMTP server. There are three options available:
None No security. This option is generally not recommended, passwords are send in plain text without encryption.
StartTLS Good security that uses the same port as unencrypted SMTP (usually 587).
TLS (formerly SSL) Good security that uses a dedicated port (usually 465).
By checking the "Enabled Event Logging" box, the subscribed email address will be able to receive log output from application events, such as data imports and indexing, via email.
This option allows administrators to email the input email address to test whether the SMTP server is configured correctly and working based on values entered in the "Email Parameters" section.
How to add Google Analytics to <Head> section of the HTML with eMuseum 6
Relevant versions: 6.0, 6.1, 6.2, 6.3, 6.4
Please note the following:
We have planned to include Google Analytics in different sections of the HTML in eMuseum version 6.5
If your eMuseum site is hosted by Gallery Systems, please reach out to Gallery Systems support and request the change instead
In eMuseum6.4.* and prior versions, there is not a configuration setting to add Google Analytics to <Head> section of the HTML, this article is going to step you through how to achieve it by modifying the Layout.tml skin file.
The file location of Layout.tml may differ for each client, especially when custom eMuseum skin is applied.
First of all, go to eMuseum Configuration page > Display Settings > Skins, or this url path http(s)://eMuseumUrl/configuration/skins, and check which skin is selected currently.
Internal implies that your eMuseum application is reading the skin files directly from <Tomcat_home>\webapps directory and that you are NOT using a custom skin.
If Internal is selected, proceed further down this guide to (2) When a custom skin is NOT applied.
If your skin is NOT "Internal", mark the skin name and locate the skin folder under <eMuseum_home>\skins folder. Proceed to (1) When a custom skin is applied.
(1) When a custom skin is applied
Navigate to <eMuseum_home>\skins\[skinName]\com\gallerysystems\emuseum\core\components
If this directory does not exist,
create this directory
Check whether Layout.tml exists under the component folder
If not, copy Layout.tml from <Tomcat_home>\webapps\[root]\WEB-INF\classes\com\gallerysystems\emuseum\core\components
paste Layout.tml to <eMuseum_home>\skins\[skinName]\com\gallerysystems\emuseum\core\components
note that if eMuseum is not the root directory, you need to replace the root folder (<Tomcat_home>\webapps\[root]) with the actual eMuseum folder name (e.g.,<Tomcat_home>\webapps\emuseum)
Open Layout.tml file
Find <t:statisticstrackingcode />
Copy and paste it to other sections of the file as needed
Save
If your eMuseum is in Production mode, restart Apache Tomcat for the change to take effect
(2) When a custom skin is NOT applied
We do not recommend modifying the source file under this directory <Tomcat_home>\webapps
Instead, please create a new folder under <eMuseum_home>\skins. The folder name will become the skin name
Download the attached .zip file below
unzip the content to <eMuseum_home>\skins folder,
rename custom_skin to a preferred skin name
skip to step 9
4. Under <eMuseum_home>\skins\[skinName], create folder META-INF and subfolders assets\css
The result should look like this <eMuseum_home>\skins\[skinName]\META-INF\assets\css
5. Under META-INF\assets\css, create a new file called custom.scssLeave the .scss file empty, eMuseum just needs it to exist
Under <eMuseum_home>\skins\[skinName]\META-INF \assets (folders you just created), create another subfolders js
The result should look like this <eMuseum_home>\skins\[skinName]\META-INF\assets\js
Under META-INF\assets\css, create a new file called custom.js
Copy and paste the empty function below to custom.js
Navigate to <eMuseum_home>\skins\[skinName], create this folder path com\gallerysystems\emuseum\core\components
The result should look like this <eMuseum_home>\skins\[skinName]\com\gallerysystems\emuseum\core\components
copy Layout.tml from <Tomcat_home>\webapps\[root]\WEB-INF\classes\com\gallerysystems\emuseum\core\components
note that if eMuseum is not the root directory, you must replace the root folder above with the actual eMuseum folder.
paste Layout.tml to <eMuseum_home>\skins\[skinName]\com\gallerysystems\emuseum\core\components
Open Layout.tml file
Find <t:statisticstrackingcode />
Copy and paste it to other sections of the file as needed
Save
If your eMuseum is in Production mode, restart Apache Tomcat for the change to take effect.
Relevant Versions: 6.0, 6.1, 6.2, 6.3, 6.4
The "Groups" feature in eMuseum6 introduces a range of functionalities aimed at enhancing the organization and browsing experience of records. This comprehensive feature enables administrators to create, manage, and nest groups based on field categories or specific search criteria. Users can easily browse through related items by grouping records, streamlining their access to relevant information.
One aspect of the "Groups" feature is the ability to create category groups. Administrators can define groups of browsable records from any module, utilizing a specific field as the basis for grouping. This categorization enables users to explore records associated with each distinct value in the selected field. By leveraging category groups, administrators can create logical associations between records and enhance user navigation within the system.
Additionally, the "Groups" feature offers search groups, empowering administrators to generate groups based on keyword searches, advanced search queries, or filtered search results. These search-generated groups provide users with direct access to result sets that match the specified search criteria.
Administrators can leverage the concept of parent groups within the "Groups" feature. Parent groups serve as containers for nesting other groups, such as search or category groups. By creating empty groups without specific module, field, or query associations, administrators can establish a hierarchical structure for organizing related groups. This nesting capability facilitates a multi-level grouping approach, allowing users to navigate through parent groups to access the associated nested groups conveniently.
This article is going to demonstrate how to create the three types of groups mentioned above:
eMuseum superuser login
Enable "Groups" page under Configuration > Page Management > Groups > Configuration tab
Go to Configuration > Page Management > Groups > Groups List tab.
Click on "Create New Group".
Enter the desired name for the group, which will be displayed on your site.
The URL path for the group will be automatically generated, but you can customize it if needed.
Automatic URL generation was introduced in v6.4
In the Parent Group drop-down list, choose whether the group should appear at the root level or as a branch of a parent group on the page.
Optionally, provide a description that will be shown on the page for this group.
Select "Parent Group"
Click "Submit"
Go to Configuration > Page Management > Groups > Groups List tab.
Click on "Create New Group".
Enter the desired name for the group, which will be displayed on your site.
The URL path for the group will be automatically generated, but you can customize it if needed.
Automatic URL generation was introduced in v6.4
In the Parent Group drop-down list, choose whether the group should appear at the root level or as a branch of a parent group on the page.
Optionally, provide a description that will be shown on the page for this group.
Select "Category Group" from the available options.
Choose the field to group on from the drop-down list.
Click "Submit"
Note that the list of grouping fields in Step (8) is generated based on the fields configured under Configuration > Data and Search Settings > Field Configuration > Search tab > Filters section.
Do an advanced search
On the Result page, click "Add New Group"
Note that the position of the button may vary depending on your eMuseum skin, but it is typically found above the result list.
Enter a Group Name for the new group.
Use the Parent Group drop-down list to determine whether the group will appear at the root level (top level) on the page or as a branch of a Parent Group.
Optionally, provide a description that will be displayed on the page for this Group.
Click "Create Group"
