joostkiens / dc-meta-tags Goto Github PK

The current default value for the Publisher tag is the site’s name. I would like to be able to choose a default value, since in my case the website’s name is not the name of a publisher.

We can already pick which DC fields show up in the edit screen. It would be nice if the fields could be reordered in the Settings page (drag & drop?)

requires_wordpress_version() is not doing its job:

1. After activation, it gets called every time WordPress runs a page, and not just upon activation – tested by adding an echo right when the function begins
2. It's not really preventing the plugin from running if the version is too low – tested with "4.3" in if ( version_compare($wp_version, "4.3", "<" ) ) {

I'll try to come up with a patch.

This plugin (version 0.2.0) was working well on my web hosting site until i upgraded it yesterday to the latest version (0.4.1).

Apparently, new update create a strange text "READ MORE" on the top of my site, this is the screenshot. I guess this error is cause by description/excerpt setting.

Although i already change it to "editable -> nothing" and input a description manually, this error is still exist.

The Dublin Core documentation indicates that it’s best to use controlled vocabulary for some fields. We should give the option of restricting the input of some fields to controlled vocabulary; or to at least suggest this, by presenting a drop-down with the controlled terms, and offering a text box to allow the input of a term not present in the vocabulary.

For instance, the Type metadata should accept one of the elements from the list at http://dublincore.org/documents/dcmi-type-vocabulary/#H7 – these are:

• Collection
• Dataset
• Event
• Image
• InteractiveResource
• MovingImage
• PhysicalObject
• Service
• Software
• Sound
• StillImage
• Text

I would be happy if I could restrict the data input to these values.

For language codes, it would be nice if the system suggested previously entered values, but allowed the entry of new values.

Autosave does not preserve the contents of the Dublin Core metadata fields.

There isn’t any theoretical reason why some Dublin Core metadata should have only one value… see for instance http://www.dublincoregenerator.com/generator_nq.html where DC metadata generation isn’t constrained to one of each for any field.

In the resources website I’m creating, we will be having pages where we offer two or more versions of a document. If we offer a text as a PDF, as LibreOffice Write and as RTF, then we should have the page tagged with
Format: application/pdf
Format: application/vnd.oasis.opendocument.text
Format: text/rtf

The same reasoning could be applied to all other metadata. In principle, let the final user decide how many of each they want, since the specification does not limit their number.

DCM_Meta_box is fired along with DCM_Admin whenever we’re in admin mode. This is unnecessary, it should only be fired when we need a meta box.

On the other hand, it’s a separate object from DCM_Admin, so if we need the options here we need to load them again. Investigate.