Question about the technical use case for Omeka-S, trying to refresh/update my conception of when to use and recommend Omeka-S moving forward:
Stated use cases on homepage:
Omeka: For individual projects and educators.
Omeka-S: For institutions managing a sharable resource pool across multiple sites.
From that framework, any individual project should choose Omeka - fairly obvious. But, for our individual project (Edison Papers) some of the newer Omeka-S features were appealing:
… Omeka S is a next-generation web publishing platform for institutions interested in connecting digital cultural heritage collections with other resources online.
… Connect to the Semantic Web: Publish items with linked open data.
Specifically, IIIF and linked data. While IIIF has the same level of support in both Classic and Semantic, the metadata profiling and collection mgmt was clearly better in Omeka-S, and the outputs would clearly integrate better into an aggregator site/service.
However, we’ve continued to encounter the problem I’ve posted about (repeatedly, sorry) in the forums with 150k items and query execution speed. I noticed in doing some Googling recently that someone had described Omeka-S (back in 2017?) as “a platform for a network of exhibits”, which I hadn’t seen or heard in that particular way before.
Based on my encounter/experience with the application code and how “universal” everything is - would it be safe at this point to say that the primary use case for Omeka-S is not browsing/searching the full collection of items (aka the shareable resource pool) and that the web/interface/queries/etc are optimized for sub-sets (aka exhibits) of that full pool?
The alternative is that I am continuing to experience local config/system issues which are making it seem that way!
Aside from the developers, would love to hear from anyone else using Omeka-S for an individual project with a large (100k+) item pool.