Started at the famous NYU Omeka/Neatline workshop of 2013, this group brings together folks interested in building digital archives and exhibits using Omeka and Neatline.
Omeka Workshop at the BGC
March 28, 2014 at 5:06 pm #554Kimon KeramidasParticipant
Since the event at the BGC (http://dml.wikis.bgc.bard.edu/omeka-workshop) is meant for this group I wanted to create a forum for people to discuss some possible ideas of things we can cover, presentations they might like to make and workshops they would either like to take or offer. So, please do so in this forum as we head towards what I hope will be an exciting and fruitful day on June 18th.
May 13, 2014 at 9:03 pm #605Kimon KeramidasParticipant
Now that the announcement has been posted and some of you have RSVP’ed for the event, remember to use this forum as a space to discuss ways to best take advantage of June 18. You can also message me through the NYCDH site or email me at firstname.lastname@example.org
Looking forward to seeing everyone next month.
June 18, 2014 at 5:38 pm #666Erin AllsopParticipant
I did not realize that there was a workshop on Omeka today! Very sad to have missed it. Will any information from this workshop be posted online? Thank you! 🙂
June 23, 2014 at 5:29 pm #689Dagmar RiedelParticipant
again, many thanks for organizing and hosting last week’s workshop at the BGC!
Following up on your suggestion that we could submit ideas about possible OMEKA workshop topics, well, here are my two pennies:
1 / OMEKA and Preservation: Best Practices for Students, Researchers, and Institutions
Since OMEKA is designed for ephemeral web publishing, I would be very interested in learning more about the options available for the backup and storage of both item records and exhibits.
The matter seems relevant to teaching because students need to learn not only about digital tools, but also about their own responsibility for storing and retaining access to their research data, whether this be the item collection which forms the backbone of their writing assignment or the writing assignment itself.
Related issues are debated among OMEKA users (e.g., http://omeka.org/forums/topic/store-files-externally), and perhaps OMEKA’s development team is already exploring these issues.
While I am comfortable with publishing exhibits on the web which are not supposed to be eternal — whatever that would mean on the web — the questions also arises whether in the long run both individual and institutional OMEKA users would need to band together to create something like a dedicated OMEKA storage space, which accepts peer-reviewed OMEKA publications (cf. the storage of archeological data in http://opencontext.org/). After all, libraries retain rarely used holdings because of their valuable contents (cf. the 80-20 rule according to which 100 percent of patrons are reading 20 percent of a library’s holdings).
2 / OMEKA vis-a-vis Copyright, Creative Commons licenses, and Open Access
The historian and archivist Klaus Graf published last week a German blog post about the legal intricacies related to the use of manuscript scans on the internet in connection with OA publications and CC licenses.
Klaus Graf’s post reminded me of your comment that at the BGC your students were mostly relying on the holdings of other institutions whenever submitting writing assignments in OMEKA.
Taken together with Stacy’s remark that the metadata of images are different from the metadata of objects, legal issues are important whenever OMEKA is used for publishing about objects owned by a range of institutions. Conversely, this topic may be of little interest to institutions that rely on OMEKA to exclusively showcase their own holdings.
June 24, 2014 at 7:47 am #691Stephen KleinParticipant
In regards to backup, I backup the digital assets (images or sound files), CSV that I used for the bulk upload and I create a data(base) dump.
June 24, 2014 at 10:05 am #692Patrick Murray-JohnParticipant
Regarding Omeka and preservation, I see two different levels: preservation proper — including things like checksums on files and maintaining that integrity, confirming sameness of two different files, etc. — and backup management. From what I gather, different groups or institutions have a variety of levels of need between those.
I can say that Omeka will probably not be doing the kinds of deep preservation that a DAMS would do — we’ll always focus on the publishing, but will be moving toward better interaction with other tools that do that level of preservation (some folks at Rice are working on a plugin to connect to DSpace, for example).
The more basic level of maintaining backups of a site, however, seems closer in line with Omeka’s mission of publishing — publishing without easy backups of a site isn’t a very good practice! That also reminds me of the conversation we had about IT needs, in particular what (I think) Jen said about the time eaten up by doing these kinds of maintenance tasks. It’s probably not within scope of our current grants, but I can imagine a plugin that would dump the db, zip up all the file assets, clean out and/or back up the log files, and save it all to one location. That might get at some of the needs in the thread you linked to.
June 30, 2014 at 9:39 am #747Erin AllsopParticipant
Thank you, Jennifer!! This is extremely helpful. Hopefully there is a workshop in the future that I can attend.
All the best,
- You must be logged in to reply to this topic.