Omeka - platform for digital cultural heritage web publishing
-
Omeka is a free, flexible, and open source web-publishing platform for the display of library, museum, archives, and scholarly collections and exhibitions.
Omeka comes in two flavors: Omeka Classic and Omeka S.
Omeka S is a web publication system for universities, galleries, libraries, archives, and museums. It consists of a local network of independently curated exhibits sharing a collaboratively built pool of items, media, and their metadata.
cf. https://github.com/omeka/omeka-s/wiki/What-to-expect-in-Omeka-S
Omeka S is an evolving project. It is a complete rewrite and reimagining of Omeka using up-to-date technologies. It also responds to the needs we have heard from Omeka users who manage many installations and work at the intersection of many content management systems and repositories.
Omeka S focuses on two core needs:
Multiple sites with easy IT administration: Omeka S has been built to address the needs of institutions that want to stand up multiple sites. These might be medium to large GLAM organizations with many subgroups that want to publish their content, or they might be universities with many instructors using Omeka in different pedagogical contexts, or any number of broad uses that call for some centralized IT management that facilitates easy creation of new sites for presentation and interpretation of many resources. A rough analogy to a WordPress networked installation works, but our design is significantly different from that model.
Data exchange: Omeka S emphasizes easy interaction between different data sources. This is most clearly reflected in our use of Linked Open Data principles. Our API functions through JSON-LD, and our metadata entry expands beyond Dublin Core and facilitate using additional vocabularies.
[...]
Omeka Classic and Omeka S will exist and be maintained side-by-side for the foreseeable future.
-
Omeka is a free, flexible, and open source web-publishing platform for the display of library, museum, archives, and scholarly collections and exhibitions.
Omeka comes in two flavors: Omeka Classic and Omeka S.
Omeka S is a web publication system for universities, galleries, libraries, archives, and museums. It consists of a local network of independently curated exhibits sharing a collaboratively built pool of items, media, and their metadata.
cf. https://github.com/omeka/omeka-s/wiki/What-to-expect-in-Omeka-S
Omeka S is an evolving project. It is a complete rewrite and reimagining of Omeka using up-to-date technologies. It also responds to the needs we have heard from Omeka users who manage many installations and work at the intersection of many content management systems and repositories.
Omeka S focuses on two core needs:
Multiple sites with easy IT administration: Omeka S has been built to address the needs of institutions that want to stand up multiple sites. These might be medium to large GLAM organizations with many subgroups that want to publish their content, or they might be universities with many instructors using Omeka in different pedagogical contexts, or any number of broad uses that call for some centralized IT management that facilitates easy creation of new sites for presentation and interpretation of many resources. A rough analogy to a WordPress networked installation works, but our design is significantly different from that model.
Data exchange: Omeka S emphasizes easy interaction between different data sources. This is most clearly reflected in our use of Linked Open Data principles. Our API functions through JSON-LD, and our metadata entry expands beyond Dublin Core and facilitate using additional vocabularies.
[...]
Omeka Classic and Omeka S will exist and be maintained side-by-side for the foreseeable future.
-
We have made progress in the packaging of Omeka S and Omeka Classic. Thanks @nebulon for their help.
If you can take some time to test, we would be grateful for your feedback on these two experimental applications to improve our work.
These are specialized applications, but I hope they will join the Cloudron App Store soon as they will be of interest to digital humanities researchers, teachers, and cultural and heritage institutions.
The difference between classic and S version of Omeka's free softwares? Basically, Omeka Classic is designed for a single site around a general theme, argument, or research question. Omeka S was created for institutions managing a sharable resource pool across multiple sites. Omeka Classic uses Dublin Core while Omeka S implements multiple vocabularies and facilitates linked open data. Omeka S is a new version that complements rather than replaces Omeka Classic. So it's important to have both
-
We have made progress in the packaging of Omeka S and Omeka Classic. Thanks @nebulon for their help.
If you can take some time to test, we would be grateful for your feedback on these two experimental applications to improve our work.
These are specialized applications, but I hope they will join the Cloudron App Store soon as they will be of interest to digital humanities researchers, teachers, and cultural and heritage institutions.
The difference between classic and S version of Omeka's free softwares? Basically, Omeka Classic is designed for a single site around a general theme, argument, or research question. Omeka S was created for institutions managing a sharable resource pool across multiple sites. Omeka Classic uses Dublin Core while Omeka S implements multiple vocabularies and facilitates linked open data. Omeka S is a new version that complements rather than replaces Omeka Classic. So it's important to have both
-
We have made progress in the packaging of Omeka S and Omeka Classic. Thanks @nebulon for their help.
If you can take some time to test, we would be grateful for your feedback on these two experimental applications to improve our work.
These are specialized applications, but I hope they will join the Cloudron App Store soon as they will be of interest to digital humanities researchers, teachers, and cultural and heritage institutions.
The difference between classic and S version of Omeka's free softwares? Basically, Omeka Classic is designed for a single site around a general theme, argument, or research question. Omeka S was created for institutions managing a sharable resource pool across multiple sites. Omeka Classic uses Dublin Core while Omeka S implements multiple vocabularies and facilitates linked open data. Omeka S is a new version that complements rather than replaces Omeka Classic. So it's important to have both
-
@jeau Are you still using this app? Just wondering if I should look into getting this published as unstable.
@girish yes, I use it experimentally. Putting it on the store as unstable will help to find new testers.
I started to implement the Ldap module, the installation seems correct. But, the admin have to activate it manually after the installation via the Omeka backend and authentication doesn't work (but I don't really know Ldap).
-
@girish yes, I use it experimentally. Putting it on the store as unstable will help to find new testers.
I started to implement the Ldap module, the installation seems correct. But, the admin have to activate it manually after the installation via the Omeka backend and authentication doesn't work (but I don't really know Ldap).
@jeau said in Omeka - platform for digital cultural heritage web publishing:
@girish yes, I use it experimentally. Putting it on the store as unstable will help to find new testers.
I started to implement the Ldap module, the installation seems correct. But, the admin have to activate it manually after the installation via the Omeka backend and authentication doesn't work (but I don't really know Ldap).
@girish & @jeau This would be awesome! Our museum is looking for new Collectionmanagement software and this might be it!
-
@jeau said in Omeka - platform for digital cultural heritage web publishing:
we have to solve the Ldap configuration
@girish & @nebulon is it possible that you guys help @jeau with the LDAP configuration so the app can be published in the AppStore?
I did an extensive research on this app and I’m pretty sure our museum will going to use this for our collectionmanagement and online availability of our collection.
-
@jeau said in Omeka - platform for digital cultural heritage web publishing:
we have to solve the Ldap configuration
@girish & @nebulon is it possible that you guys help @jeau with the LDAP configuration so the app can be published in the AppStore?
I did an extensive research on this app and I’m pretty sure our museum will going to use this for our collectionmanagement and online availability of our collection.
-
@girish @jeau We can't wait to see this as an app on Cloudron. Just for testing purposes and to get familiar for our volunteers (our museum is driven only by volunteers like me) I installed it in a LAMP app and got it pretty soon online.
Will keep my experiences here so the app can profit from it:
missing components for the "Extract Text"-module:
Extractor Available
catdoc No
docx2txt No
lynx No
odt2txt No
pdftotext No
filegetcontents Yes -
@girish @jeau We can't wait to see this as an app on Cloudron. Just for testing purposes and to get familiar for our volunteers (our museum is driven only by volunteers like me) I installed it in a LAMP app and got it pretty soon online.
Will keep my experiences here so the app can profit from it:
missing components for the "Extract Text"-module:
Extractor Available
catdoc No
docx2txt No
lynx No
odt2txt No
pdftotext No
filegetcontents Yes@imc67 Hmm, these would need to be installed in the OS, right? https://omeka.org/s/modules/ExtractText/
I've never packaged an app for Cloudron; I wonder how one would include these components?
A life lived in fear is a life half-lived
-
@imc67 Hmm, these would need to be installed in the OS, right? https://omeka.org/s/modules/ExtractText/
I've never packaged an app for Cloudron; I wonder how one would include these components?
-
@imc67 Hmm, these would need to be installed in the OS, right? https://omeka.org/s/modules/ExtractText/
I've never packaged an app for Cloudron; I wonder how one would include these components?
@imc67 @scooke you are right, this components need to be pre-installed in the OS. I can add them.
On the Omeka S app, you can install manually themes and plugins (modules) inside the
/app/datadirectory. I installed LDAP module and I hesitated to install EasyInstall module whitch allows to install Omeka S modules and themes from https://omeka.org and from the web (https://github.com and https://gitlab.com). But it isn't possible to check all the dependencies required by all these components and I am afraid that the users do not pay attention to this issue.However, I'm thinking of check the dependencies required by the modules of the official modules list. Extract Text is present in this list.
-
@seeker I also think that many users will be interested in simply manage this kind of tools useful for heritage and digital humanities. For example Cantaloupe IIIF Image Server or Mirador Viewer that I already added to App Wishlist.
-
@seeker I also think that many users will be interested in simply manage this kind of tools useful for heritage and digital humanities. For example Cantaloupe IIIF Image Server or Mirador Viewer that I already added to App Wishlist.
-
I have forked the app repo from @jeau into our namespace at https://git.cloudron.io/cloudron/omeka-s-app so lets collaborate on that to get the app out there
Thanks already for all the work done!
@nebulon I added the optional dependencies of Omeka S and the dependencies required by the modules listed on the official website.
However, I have this error when I try to push this commit to our repository:
! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'https://git.cloudron.io/cloudron/omeka-s-app.git' -
@nebulon I added the optional dependencies of Omeka S and the dependencies required by the modules listed on the official website.
However, I have this error when I try to push this commit to our repository:
! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'https://git.cloudron.io/cloudron/omeka-s-app.git'
