raboofI volunteer as 'IT person' for a museum in its early days, (https://www.eicas.nl - @EICAS).
I would love to connect with other "museum people" and "museum IT people", here and elsewhere.
Any boosts/recommendations welcome!
Stevan@raboof @EICAS I don't work in/for a museum, but our small community does run its own digital archive based on Omeka, with which I am involved. It's been running since 2011. Of course, COVID has meant very little activity but we hope to restart training sessions soon.
The archive was originally on dspace but after we'd learnt a bit, and Omeka matured, we migrated. It wasn't too hard thanks to common Dublin Core metadata & Free Software not locking us in.
The archive was originally on dspace but after we'd learnt a bit, and Omeka matured, we migrated. It wasn't too hard thanks to common Dublin Core metadata & Free Software not locking us in.
@withaveeay interesting! I'm actually exploring collection management workflows and systems right now. Definitely adding #Omeka to my list, though it sounds like it is more targeted to archives where for example #CollectiveAccess might be more suitable for a museum. To be honest I'm still learning what the practical differences are between the two though :)
@raboof In an institutional context, with IT support, DSpace may well be the repository system of choice. Omeka acts as both a repository and resource manager.
@raboof I should add that for your requirement, DSpace may also have the edge as it enforces a defined workflow, while Omeka is much more fluid & depends on users adhering to procedures rather than an enforced process