I understand we cannot delete or modify Dublin core metadata fields. (http://omeka.org/codex/Customizing_Items_and_Metafields)
However, has anyone ever been able to suppress those fields in the administrative upload/edit interface for item ingestion. We are considering limiting the number of visible fields for our contributors when they are adding content.
Hi, I was wondering if you were ever able to figure out how to suppress Dublin Core fields in the admin interface. I can't figure out which files I need to edit. Thanks for any information you can give me.
Best, Jen
Unfortunately there is currently no way to delete or hide specific Dublin Core fields. We're open to adding this as a feature to a future release of Omeka, though, if there is enough interest. I've added a ticket for this to our Trac, but haven't associated it to a milestone yet.
Does this mean it's not possible to edit the fields in the PHP or that it's merely not possible to edit the fields from the GUI?
Hi,
Looks like its not got a lot of support, but my team would like to be able to simplify the Core data entry by limiting the number of fields normally exposed. Can I resurrect this issue?
Likewise. The extensive screen space occupied by unused element fields of the Dublin Core, and especially those added by the Extended version and the Zotero plugins, is a major obstacle to Omeka functionality. Scrolling down the page to reach to save button consumes a considerable amount of time. We are reluctant to remove the unused fields in the database as a work-around for known reasons.
Thanks in advance for any forthcoming solutions.
Omeka (as you've all noticed) doesn't have any remotely convenient way to remove Elements from the admin form for Items.
This is probably a perfect use case for a plugin, but Omeka doesn't quite currently expose the kind of functionality a plugin would need to be able to do this.
This request really hasn't gotten any action since Jeremy's post a year ago, but I think it's a feature that would make sense for Omeka 2.0 (the next major version), whether as a plugin or core feature.
In the realm of temporary workarounds, it probably wouldn't be too difficult to come up with something in JavaScript or CSS that removes the unwanted form elements from the page. It's not the ideal solution, but it's something somebody could work on without waiting for a new Omeka version.
I am having a similar situation. Looking for a workaround.
Essentially, when adding an item, the Dublin Core screen (admin side) I would like the ability to rearrange the data display, or remove unwanted core elements from the admin area to limit the confusion for some.
Understanding that this is a possible future feature, what calls up this information? I mean I have checked every file including the .sql files in the omeka core and don't see where this information is being called from. There is not a php file floating around that organizes the Dublin Core data?
You must log in to post.
Omeka is a project of the Roy Rosenzweig Center for History and New Media, George Mason University. Omeka and the Omeka logo are registered trademarks. Copyright © 2007–2012 CHNM.