Add more Dublin Core meta tags

When someone does get to this would be good to bring in some code from http://openconcept.ca/blog/mgifford/adding_dublin_core_metadata_to_drupal

I do think this is something that will fit nicely with all of the RDF work going on in the drupal community.

Mike

thanks!

I've added some information on Dublin core and Google Scholar's requirements here.

Subscribe

We require some of these tags for our project so is it alright if I go ahead and add a few and then provide a patch?

I don't think I understand your response. Are you telling me that in branch 6.x-3 these fields are already available? Or that I should make the changes in this code.

Also, I noticed that the node [tokens] don't always seem to resolve properly. Is there an area in the code that I could check out to figure out how they are being parsed?

Thanks

Shane

PS - I've got a bunch of the fields pretty much working now (awesome code and easy to add stuff into)

While I agree that adding more Dublin Core tags would be a good thing, I think all of these properties may be better served by a separate add-on module (similar to the way Kiam had separated it before). In order to have full support for DC, there are a shocking 18(!) tags that could be added. That's twice as many as all the other metatags combined. Considering actual usage of DC is mostly theoretical at this point, I'd prefer these were separated even further from the bulk "extras" module that includes location and the (now deprecated) ICRA tag. Similar to how the verification tags are separate, making "nodewords_dublin_core" seems like a good idea.

I've been contemplating re-architecting how the bundled meta tags are loaded. My current idea is to handle them via include files rather than separate modules, making it easier to turn on the specific tags, or groups of tags, via a checkbox rather than having to enable a whole extra module. In this world, I'd probably separate the Dublin Core list into two - common (what's already included) and advanced (all of the ones not currently supported), then let those few individuals who specifically want them to easily enable them.

Anyway, this is a discussion for v1.14.

An issue to discuss / plan my plans to rearchitect Nodewords: #1379598: Rearchitect to use include files instead of submodules

Lets see about adding some more to v1 as-is, do the re-engineering later.

Related issue for Metatag: #1491616: Add new meta tag: Dublin Core

Some meta tags that could be quickly added from the 1.1 specs:

• coverage
• format
• identifier
• language
• relation
• rights
• source
• subject
• type (default to "text/html")

It may also be worth adding an option to output the tags in dc.tag, dc:tag or dcterms.tag, this should be easy to do.

Am hoping to get clarification from someone at the DCMI on what the best option is regarding the meta tag namespace.

Related: #1751318: Correct the Dublin Core tags

I'm aiming to match Metatag with the next release, so the following Dublin Core tags will be added:

• coverage
• format
• identifier
• language
• relation
• rights
• source
• subject
• type

The new tags should be added to a new submodule, to mirror Metatag, and then the existing Dublin Core meta tags can be moved into the new module via #1852546: Move Dublin Core meta tags into their own submodule.

Clarified the issue.