#242 ✓resolved
Walter McGinnis

Add DC-HTML to all item detail pages to support Zotero, etc.

Reported by Walter McGinnis | November 8th, 2009 @ 12:16 PM | in 1.3 (closed)

Use http://dublincore.org/documents/dc-html/ example #6 as spec for adding a Kete item's Dublin Core to each item detail page.

  • create a helper method to output an abbreviated form of the Dublin Core, that which is useful for citation, associated with an item
  • add a call to use this helper method in views/layouts/application template in the HTML head section, it should include logic that determines if the page is 1) a zoom item via its controller, 2) a show action, and 3) a public version and only add the metadata if those criteria are satisfied.
  • wrap this call to the helper method in a named caching block
  • add the named caching block to the appropriate caching expiration methods via updating SHOW_PARTS constant

Comments and changes to this ticket

  • Kieran P

    Kieran P December 21st, 2009 @ 10:01 AM

    • Assigned user changed from “Walter McGinnis” to “Kieran P”
  • Walter McGinnis

    Walter McGinnis December 22nd, 2009 @ 09:33 AM


    Looking at http://github.com/kete/kete/commit/44330d82a1ba2708f0cc25b0f43587ca... -

    • Language, we don't know for sure what the language of the ITEM is yet. So I would opt not to include it and I certainly wouldn't assume that the item's language is the same as what the user happens to be looking at. Language is optional, I believe. If it absolutely must be specified, I would make it the site default locale.

    • Don't include DC.description. My understanding is Zotero doesn't support it anyway, it is potentially quite large (PDFs, etc.) and we don't have a use case where it is necessary.

    • Contributors. If there is more than one contributor, list the LAST contributor and "et al" and that's it. Otherwise we could end up with very long list of contributors that Zotero will simply ignore anyway.

    • Format. I think it is misleading to use text/html for all items. Just drop it for now.

    I'm trying to strike a balance between bit bloat and usefulness to outside services like Zotero. We don't need to put all fields in, just the ones used by common services. What would be better, but isn't supported by OAI PMH (and not by Zotero either, from my understanding) is simply pointed the outside service at an alternative view of the data, i.e. its full OAI-PMH record.

    On http://github.com/kete/kete/commit/828c0fc96549976d9d6258875f43e588..., looking at url_to_item, I believe this is reinventing the wheel. Wouldn't item.url_for_dc_identifier do the job? Actually, link_to_item smells redundant to me as well.

    For this:

    <%= meta_tag :name => 'content-language', :content => I18n.locale %>

    As alluded to above, I believe it is jumping the gun as we don't have content translation in place yet (just because the interface is translated, does not necessarily mean the content reflects this yet). I would comment this out, but keep it around for reference.


  • Kieran P

    Kieran P December 22nd, 2009 @ 10:34 AM

    • State changed from “new” to “resolved”

    This work has been completed and merged to master. Resolving ticket.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Kete was developed by Horowhenua Library Trust and Katipo Communications Ltd. to build a digital library of Horowhenua material.

People watching this ticket