Omekas

Overview I tried outputting Delete records with the Omeka S OAI-PMH Repository module, so this is a personal note for future reference. Background By using the following module, you can build OAI-PMH repository functionality. https://omeka.org/s/modules/OaiPmhRepository/ However, as far as I could confirm, there did not appear to be a feature for outputting Delete records. Related Module Omeka’s standard features do not seem to include functionality for storing deleted resources. On the other hand, the following module adds functionality to retain deleted resources. ...

Overview In the following article, I introduced a page for visually reviewing Omeka S themes. The program used to create the above page has been published in the following repository. https://github.com/nakamura196/OmekaS Summary We hope this is helpful for similar work.

Overview I looked into how to publish 3D models in Omeka S, so here are my notes. As a result, I was able to handle 3D models in Omeka S as shown below. https://omeka.aws.ldas.jp/s/sample/item/43 Versions The versions of Omeka S and modules used are as follows. Omeka S 4.1.1 Common 3.4.62 IIIF Server 3.6.21 Universal Viewer 3.6.9 Module Installation Install the Common, IIIF Server, and Universal Viewer modules. Module Configuration Configure two settings for the IIIF Server module. ...

Overview In Omeka S, I encountered an issue where the error message “CSRF: Value is required and can’t be empty” was displayed when trying to save an item associated with many media, and saving would not complete. This article explains how to address this error. Related Articles This is mentioned in articles such as the following. It appears to be a known error, and it is stated that php.ini needs to be modified. ...

Overview During the Omeka S update process, the following error occurred. Fatal error: Uncaught ArgumentCountError: Too few arguments to function Omeka\View\Renderer\ApiJsonRenderer::__construct(), 0 passed This is a personal note on how to address this error. Solution The solution was found at the following link. https://forum.omeka.org/t/upgrade-from-4-0-4-to-4-1-failed/22281 Specifically, uninstalling the Next module resolved the above issue. Summary I hope this serves as a useful reference for those encountering the same issue.

Overview This is a personal note on updating Omeka S. Please also refer to the following official documentation. https://omeka.org/s/docs/user-manual/install/#updating Preparation: Backup Before performing update operations, be sure to create backups of the database and all files in case of unforeseen circumstances. 1. Database Backup Create a database dump file using the mysqldump command or similar. # m y m s y q s l q d l u d m u p m p - u - u d b [ _ D u B s e u r s e - r p n a o m m e e ] k a - _ p s _ [ d D b B > n a o m m e e ] k a > _ s [ _ o b u a t c p k u u t p . f s i q l l e n a m e ] 2. File Backup Back up (duplicate) the entire Omeka S installation directory. ...

Overview This article introduces how to export only specific items with selected fields using Omeka S BulkExport. Here, we will limit the export to items that have “Table Of Contents (dcterms:tableOfContents)” and export only “Title (dcterms:title)” and “Identifier (dcterms:identifier)”. Related The following article explains the overview of the Omeka S BulkExport module. This time, I will explain based on a specific use case. Method Navigate to the following path. ...

Overview This is a personal note on how to retrieve the URL of site pages where items are published in the Omeka S OaiPmh Repository module. Background The following article introduces how to create custom vocabularies using OaiPmhRepository. https://nakamura196.hatenablog.com/entry/2021/07/25/222651 Please refer to it as well. Retrieving the URL of Site Pages Where Items Are Published Before Fix In a certain customization case, the site page URL was retrieved as follows. This does not work properly when something other than dcterms:identifier is configured in the Clean URL module. Additionally, hardcoded paths like /s/db/record/ can be seen. ...

The steps to enable detailed error display in Omeka S are as follows. By making this setting, specific error messages and details will be displayed on the “Omeka S has encountered an error” page. Additionally, PHP-level errors and warnings will also be displayed on the page. This is intended to make it easier to identify and resolve issues during development, but for security reasons, it is recommended not to use this in production environments. ...

Overview When performing bulk data registration using Omeka S’s BulkImport, you can configure various settings for the registration method. While these settings can be configured each time you upload, using pre-registered settings can help reduce errors made by operators. Here, I introduce a configuration example for bulk registration when associating IIIF images with already registered items. Item Example Create an item with sample as the dcterms:identifier as shown below: ...

Overview When using the BulkImport module with the combination of PHP 8.1.29 and Omeka S version 4.0.4, the following error occurred. F S # a t 0 t a a c / l k h o e t m r r e r a / o c x r e x : : x / U w n w c w a / u o g m h e t k a T - y … p e E r r o r : m b _ s u b s t r ( ) : A r g u m e n t # 1 ( $ s t r i n g ) m u s t b e o f t y p e s t r i n g , n u l l g i v e n i n / h o m e / x x x / w w w / o m e k a - s / m o d u l e s / B u l k I m p o r t / s r c / P r o c e s s o r / R e s o u r c e P r o c e s s o r . p h p : 1 0 7 9 I have not been able to identify the root cause at this point, but I will describe the workaround. ...

Overview When distributing IIIF manifests using the Omeka S IIIF Server module, the following CORS error occurred in external viewers. A c c e s s t o f e t c h a t ' h t t p s : / / x x x / i i i f / 2 / 0 9 f d 2 9 d 5 - 8 4 9 7 - 4 d e f - a 6 4 d - c a 1 0 4 2 8 4 f 9 0 d / m a n i f e s t ' f r o m o r i g i n ' h t t p s : / / u n i v e r s a l v i e w e r . i o ' h a s b e e n b l o c k e d b y C O R S p o l i c y : N o ' A c c e s s - C o n t r o l - A l l o w - O r i g i n ' h e a d e r i s p r e s e n t o n t h e r e q u e s t e d r e s o u r c e . I f a n o p a q u e r e s p o n s e s e r v e s y o u r n e e d s , s e t t h e r e q u e s t ' s m o d e t o ' n o - c o r s ' t o f e t c h t h e r e s o u r c e w i t h C O R S d i s a b l e d . ...

Overview When installing the CleanUrl module on Omeka S 4.1.x, the following error occurred. L S a e m r i v n i a c s e \ S w e i r t v h i c n e a M m a e n a " g O e m r e \ k E a x \ c A e c p l t " i o c n o \ u S l e d r v n i o c t e N b o e t C c r r e e a a t t e e d d E . x c R e e p a t s i o o n n : R e s o u r c e i d ' O m e k a \ C o n t r o l l e r \ S i t e \ P a g e ' a l r e a d y e x i s t s i n t h e A C L This issue had also been reported in the following forum. ...

Overview The following error occurred during Omeka S operation. ' s e s s i o n . n a m e ' i s n o t a v a l i d s e s s i o n s - r e l a t e d i n i s e t t i n g This same issue was reported in the following forum. ...

Overview Custom Ontology is a module that allows you to add custom vocabularies when standard ontologies such as LOV, schema.org, and W3C are not available. For basic usage of this module, please refer to the following. https://nakamura196.hatenablog.com/entry/2021/07/24/235050 For how to update vocabularies that have already been created using this module, please refer to the following. This article explains how to add classes and properties to an already created vocabulary. ...

Overview To address the issue where full-text search in Japanese does not work well with Omeka S’s standard functionality, I have created the following module. https://github.com/nakamura196/Omeka-S-module-FixCjkSearch This module had stopped working with the latest version of Omeka S at the time of writing (v4.1.0), so I released an updated version of the module. https://github.com/omeka-j/Omeka-S-module-FixCjkSearch/releases There may be some incomplete aspects, but I hope this serves as a helpful reference. References For information about full-text search issues with Japanese, please also refer to the following article. ...

Overview I investigated accent sensitivity in Omeka S partial match search, and here are my notes. Symptom For example, when items containing the string “tako” (in hiragana) are stored, searching for “tako” in hiragana, katakana, or with dakuten (voiced mark) variations all return the same results. Cause The issue appeared to be caused by the default collation “utf8mb4_unicode_ci” set during installation. Specifically, this collation is “case-insensitive” (does not distinguish between uppercase and lowercase) and “accent-insensitive” (does not distinguish between accented and unaccented characters), which is why hiragana, katakana, and dakuten variations return the same search results. ...

Overview I updated the Omeka S theme using Bootstrap 5. Here I introduce the features added in this update. https://github.com/ldasjp8/Omeka-S-theme-Bootstrap5/releases/tag/4.0.2 New Features Advanced Search Button Link Configuration I added an “Advanced Search URL” option to the theme settings screen. In the example above, a setting is configured to navigate to the “page/advanced” page. Specifically, when clicking the “Advanced Search” button shown below, it navigates to the URL configured here. (If not configured, it navigates to Omeka’s standard advanced search page.) ...

Overview This article explains how to perform partial match searches using filters added through the Advanced Search module. In the example above, the query string “toru” matches items with the title “abc title”. Background The Advanced Search module allows you to flexibly configure search conditions and facets. https://omeka.org/s/modules/AdvancedSearch/ In particular, when combined with the “Reference” module, faceted search like the following can be achieved. You can also add filters. However, when performing partial match searches with filters, additional configuration is required. ...

Overview This article explains how to specify which items to display in search results, as shown below. Configuration In the default settings, the “Heading” displays the title (dcterms:title) and the “Body” displays the description (dcterms:description), as shown below. You can configure which items to display for “Heading” and “Body” respectively by changing the following section in the per-site settings screen. For Advanced Search Even when using the Advanced Search module, these settings are inherited. ...