- This topic has 1 reply, 2 voices, and was last updated 3 years, 3 months ago by
.
-
Posts
-
Thanks for setting this up so much, Leah! Really helps with getting to grips with Omeka 😀 In terms of customisation of metadata and adding other standards or custom metadata, is it the plugins that support this? Is this part of the reason our community archives teacher preferred WordPress as the ability to customise metadata was already “in built” so to speak? If this will be answered in the next lesson or future lessons, I’m happy to wait until the next lessons! 🙂 🙂
This is Chloë by the way!
Hi Chloe! Modifying Item Types (there’s a video about that in the next unit, which I have belatedly added) is really what allows you to customize metadata elements in Omeka Classic. Dublin Core is the foundational metadata set no matter what, but for each item type, you can specify which DC elements you want to be available. WordPress has almost no built-in metadata–what we filled in during class was facilitated by a plugin, and then it couldn’t be published properly because another plugin wasn’t activated to actually publish that metadata. (Essentially, it is a lot more work to create and publish metadata in WordPress than it is in Omeka.)
Our community archives professor ultimately chose WordPress because they did not believe that Omeka had the ability for outside collaboration. However, that is not true–there is a very robust plugin called “Contribution” that allows community members to contribute their own items to an Omeka site.
- You must be logged in to reply to this topic.
