It’s been a while, but I’ve been busy doing some scanning as well as working on other projects. Forgive me for neglecting this blog!
Just read a cool thing on the Omeka development blog. I know it’s a baby accomplishment, but it’s my own way of getting into the more technical conversations about websites and I’m proud of myself nonetheless. Here’s how I changed the heading “Dublin Core” to “Description” for the items. (And here is the source I used: https://groups.google.com/forum/?fromgroups#!topic/omeka-dev/raQ5FEok3rc)
- Find the “item-metadata.php” file. Hint: it’s in application/view/scripts/
- [Write a description of what this file does…]
- Copy that file to a new location – theme-name/items/
- As noted, moving this file to a new location helps preserve this change through future upgrades to Omeka. I’m sure if I changed the file in it’s original location, it would have worked – however, the change would have been lost in a future upgrade to Omeka itself.
- Here is the beginning of that php file:
<div class="element-set"> <h2><?php echo html_escape(__($setName)); ?></h2>
<?php foreach ($elementsInSet as $info): $elementName = $info['elementName']; $elementRecord = $info['element']; if ($info['isShowable']): ?> ...
- This line is what adds the heading to the item:
<h2><?php echo html_escape(__($setName)); ?></h2>'
- I’ve removed the variable $setName and used the literal value “Description” instead.
That’s that! I’m quite happy with this minor change and glad that I managed to even read that helpful comment by one of the developers. Things I’ve learned:
- Apparently themes trump the built in displays. Somehow omeka must look at the files in theme ‘first’ and then revert to the standards provided in the application itself. Very interesting.
- Learned where to look to change somethings. Very intriguing.
I’ve got a very long list of things yet to learn, but so far so good!