Omeka

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 investigated how to publish videos with Omeka S, so this is a memorandum. Standard Features Omeka S supports video out of the box. Below is an example using the standard features. I used the following mp4 file: https://file-examples.com/storage/fe4e1227086659fa1a24064/2017/04/file_example_MP4_480_1_5MG.mp4 Specifically, the <video> tag was used as follows: < d / i d v v i i < v v c d a i > l e d a o h e s r o s s e > = r f " c = m = " e " h d h t i t t a t p - p s r s : e : n d o e o m r m e e k f k a i a - l - d e d . " . a > a w w s s . . l l d d a a s s . . j j p p f f i i l l e e s s o o r r i i g g i i n n a a l l 5 5 0 0 6 6 0 0 f f 3 3 b b a a 2 2 5 5 3 3 7 7 6 6 7 7 6 6 7 7 4 4 6 6 a a 7 7 a a a a 6 6 9 9 c c 9 9 8 8 8 8 4 4 c c 6 6 4 4 d d a a a a c c 3 3 0 0 0 0 b b . . m m p p 4 4 " " > 5 c 0 o 6 n 0 t f r 3 o b l a s 2 = 5 " 3 " 7 > 6 7 6 7 4 6 a 7 a a 6 9 c 9 8 8 4 c 6 4 d a a c 3 0 0 b . m p 4 < / a > Similarly, when uploading a .mov file, it played successfully, though this may be browser-dependent. ...

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. ...

Overview This article introduces how to create a custom search page like the following in Omeka S. Background For creating search pages in Omeka S, I previously introduced a method to limit filter items on the advanced search screen. However, as shown in the overview, there are cases where you want to create a search screen that lists only specific items. For creating such a search page, you can use the “Advanced Search” module. ...

Overview When attempting to install the Clean Url module on Omeka S built with the following environment: PHP Version: 8.3.2 Omeka S Version: 4.0.4 Clean Url Version: 3.17.7 The following message was displayed: D e p r e c a t e d : C r e a t i o n o f d y n a m i c p r o p e r t y C l e a n U r l \ R o u t e r \ H t t p \ C l e a n R o u t e : : $ p r i o r i t y i s d e p r e c a t e d i n v a r / w w w / h t m l / v e n d o r / l a m i n a s / l a m i n a s - r o u t e r / s r c / S i m p l e R o u t e S t a c k . p h p o n l i n e 2 8 5 To address this issue, the above message could be hidden by partially modifying the /modules/CleanUrl/src/Router/Http/CleanRoute.php file as described below. ...

Overview This article explains the “File Sideload” module for batch uploading images to Omeka S. https://omeka.org/s/modules/FileSideload/ The official manual is available at the following URL: https://omeka.org/s/docs/user-manual/modules/filesideload/ Module Installation It can be installed using the standard method. https://omeka.org/s/docs/user-manual/modules/#installing-modules Module Configuration After installation, you will be navigated to the following configuration screen. Here, specify the path to the folder for uploading images for batch registration. Depending on permissions, you should be able to specify any arbitrary path. ...

I am sharing a response from ChatGPT4 about the differences between Omeka Classic and Omeka S. I hope it serves as a useful reference. Omeka and Omeka S are open-source web publishing platforms for building digital collections and exhibitions. Both are widely used by academic institutions, libraries, museums, archives, educators, and cultural heritage organizations. However, Omeka and Omeka S differ in their design and intended use. Omeka (Classic) Target audience: Best suited for individuals and small-scale projects. Suitable for school projects, personal research, and small archival collections. Features: Easy to install and provides an intuitive admin interface. Focused on individual websites and projects, specializing in single site management and exhibition creation. Use cases: Best for exhibiting small digital collections and educational projects. Customization is possible through plugins and themes, but it is not suited for integrated management of multiple projects or collections. Omeka S Target audience: Best suited for organizations with multiple projects and collections, such as universities, libraries, and museums. Features: Omeka S is designed to enable the creation and management of multiple sites. With a single installation, it allows sharing, reusing, and linking resources across different projects and collections. Use cases: Best for large institutions that have multiple digital collections and exhibitions and want to manage them in an integrated manner. It provides more advanced features including API support, advanced search functionality, and Linked Open Data support. Key Differences Intended use: Omeka Classic is designed for small-scale projects and individual users, while Omeka S is designed for organizations and institutions with multiple projects and sites. Functionality: Omeka S provides more advanced features such as multi-site management, Linked Open Data support, and data access via API. Extensibility and interoperability: Omeka S aims for broader data integration and interoperability by sharing items across collections. The choice depends on the scale of the project, its purpose, and the type of data being managed. Omeka Classic is suitable for small-scale projects and personal use, while Omeka S is suitable for organizations handling multiple projects and large datasets. ...

Overview On the advanced search screen for each site built with Omeka S, users can select a property and search for specific values. With the default settings, all properties registered in Omeka S are displayed, which can make it difficult to use. This article introduces how to limit the properties shown as selectable options, as shown below: This article targets Omeka S version 4.0.4. Documentation The relevant documentation can be found here: ...

Overview Bulk Import is a module for batch registration of items and media in Omeka S. https://github.com/Daniel-KM/Omeka-S-module-BulkImport It has been continuously updated and has become quite convenient, so this is a memo. Installation It can be installed in the usual way. However, the Log module must be installed beforehand. https://github.com/Daniel-KM/Omeka-S-module-Log Usage Here, I will introduce an example of registration using a CSV file. Configuration First, access the following and click the edit icon. ...

Overview When loading a Presentation API v2 manifest file like the following into Mirador 3, a display error occurred. https://gist.githubusercontent.com/nakamura196/42fb6bca6a9fa137234c334cb313fc58/raw/4188ebccb7406ff5132331a4fecc4ace8bdd7ebc/ng.json Below is the display in Mirador 3. I investigated the cause and workaround, and am sharing the findings here. Cause The following error message was displayed. Despite providing IIIF v2 input, it appeared to be interpreted as v3. E r r o r a a a a a a a a a a : t t t t t t t t t t A P A t t c i h i h F r r . . a n n u I o r p g n d ( d ( n I p a a e v e d e d c I e y r t a x e x e t F r . s L s . f . f i t m e a e j a j a o v y a b s s u s u n 3 V p ( e . : l : l . a P l j 6 t 8 t m l l r s 7 M 1 M a o u < o ( : : e : e p c e a p M 1 2 m 4 m T a . n e a 6 5 o 0 o o l t o r n 2 i i P i s n t i : z z r z : y y f 1 e e o e 1 m V e 2 . . p d 2 o a s j j s 6 u l t s s p : s u R : : ( r 2 > e e 1 1 O o 0 ) . s 2 2 p p t o 3 3 e e s u : : n r : r 2 2 S t 1 c 0 0 e y 2 e ) ) a 3 . d v : t r a 2 s a l 9 : g u ) 3 o e 5 n : V m 2 i u 8 e s ) w t e r h . a j v s e : 3 a 9 n : 1 a 2 r ) r a y a s t h e v a l u e f o r a g i v e n l a n g u a g e . This appeared to occur when the canvas label was written in object format, as shown below: ...

Overview IIIF Viewers is one of the modules for Omeka S. https://github.com/omeka-j/Omeka-S-module-IiifViewers The latest release is available here: https://github.com/omeka-j/Omeka-S-module-IiifViewers/releases/latest I made several updates this time, so this is a memorandum. Universal Viewer Version Update I updated Universal Viewer to v4.0.25. Additionally, I documented how to update Universal Viewer in the following section of README.md: https://github.com/omeka-j/Omeka-S-module-IiifViewers?tab=readme-ov-file#compilation-of-universal-viewer This was based on the documentation in the following module: https://github.com/Daniel-KM/Omeka-S-module-UniversalViewer I also documented how to update Mirador, but since the latest version was already installed, no update was performed. ...

Overview In Omeka S, you can set public/private settings for each resource (item sets, items, media, etc.), but for files such as images associated with media, even if the private setting is applied, anyone who knows the file URL can access it. Typically, the URL follows this pattern: <Omeka installation directory>/files/original/<hash value>.jpg If the private setting is applied to the media, it would be rare for this file URL to be known, but there are cases where you want to avoid a situation where “anyone with the link” can access it. ...

Overview To send emails from Omeka S running on Amazon Lightsail, it appears that email sending configuration is required. This article introduces how to use Amazon SES. https://aws.amazon.com/jp/ses/ The following forum discussion was helpful. https://forum.omeka.org/t/configuring-sendmail-or-smtp-for-omeka-s-on-amazon-lightsail/19335/1 Amazon SES Configuration Configure Amazon SES by referring to the following site. https://qiita.com/Shun_konno/items/f51ae599b68e0d2d36ea Omeka S Configuration Edit the Omeka S local.config.php file as follows. < r ] ? e ; p t h u p r ' ] ' ] n l , m , o a ' [ g i u O g l ' s ] t e ' t e , h r r _ e ' L = a c r o > n ' o ] = g s t o m , s > [ p y p p e s o p t l t [ e r e i ' ' ' ' ' e ] t t t ' o n h p c c t , i t ' n a o o o o e n i = s m s r n n _ g n = > ' e t t n n ' ' ' q s g > ' ' ' e e u p s u . s ' = c c s a s i . [ s > = = = t t e s l t . ( m > > > i i r s ' ' a t [ o o n w s p ' ' 5 n n a o = ' s e 8 _ _ m r > n , e m 7 c c e d e s a , l o ' ' t e - i a n r d s l s f = = = u e m - s i > > > e d U t s ' g , ) s p m ' ' ' ' e - t y y t u p = = o o l S s . > > u u s M e u r r ' T r s ' [ - - , P ' - p s s , e l e e a a s s s i - - t n s s - ' m m 1 , t t . p p a - - m u p a s a z e s o r s n n w A a a o n w m r y s e d . ' ' n c , , a o m m e ' , S S S P A E E S o u S S L S r t E t h S S t S e M M y s n T T p S u t P P e M p i T p c u p P o a s a ' r t e s t s t i r s l e e o n w s r d n a o ' v m r e b t e d r r y y e p c e S e o n E m d S m p e o ( n i e d n . e t g d . ) , 5 8 7 ) For host, specify the Amazon SES SMTP server endpoint corresponding to the AWS region you are using. The example uses the us-east-1 region endpoint, but change it as needed. For username and password, use the SMTP credentials generated in Amazon SES. Summary We hope this is helpful when using Omeka S with Amazon Lightsail. ...

Overview I created a page for visually browsing Omeka S themes. https://satoru196.notion.site/satoru196/6f898ed1352e4c9fa013eee635cbabf4?v=02cab757b6cf4df6bfbedfeb85eca0a5 The following site is convenient for searching Omeka S themes: https://daniel-km.github.io/UpgradeToOmekaS/omeka_s_themes.html However, I thought it would be even more convenient to be able to see the appearance of themes and their star counts in a list view. Using the source data from the site above, I created this new page: https://github.com/Daniel-KM/UpgradeToOmekaS/blob/master/_data/omeka_s_themes.csv How It Was Created GitHub I used the GitHub API to retrieve the last update date and star count for each repository. To use the GitHub API, I created a Personal Access Token (PAT): ...