I’'m looking into the application of Omeka for multiple different collections that will however be related in several ways, by (sub)topics, involved persons, locations, and context. (To make it a little more concrete, think historical conflict sites of the 20th century and ~10 related international collections of institutions and memorials.) From reading this blogpost (much more info is not easily found) I get the impression the S version might be better for our needs than the current 2.x (classic). We plan to use the platform to primarily interface to our own front-end applications first, so website publishing isn’t immediate priority, but flexible catalog authoring by multiple users definitely is, and a LOD/ RDF-based approach to relations and ontology will be also. We will have to develop and adjust on top of any way we choose, but of course we want to reduce development repetition.
Because of several unknowns and the expected heterogeneity of the datasets, we (=few people, still) can’t really oversee how best to gradually upscale from single ‘clients’, to interface to joined collections or separate client installs, nor what ontology will emerge. But since we’re at the start with 0 data to migrate still, we might choose the option that can best ‘grow along’ in agile fashion. In that long-term context, a Graph-based core approach seems better to me than a RDBMS one.
From the above, do you think Omeka S the better option to start, or would you still recommend to start with Omeka Classic (or perhaps Ozmeka) and take leverage from its larger set of stable add-ons for the time being, and just plan migration & development steps?
Thanks a lot for any advice!