On Tue, Jul 18, 2017 at 09:02:44PM +0000, Alan Orth wrote:
> Keep in mind that the language needs to match the metadata record as well
as the "value." This could be en_US, null, or several other things.
> It's one of the implementation details that makes it hard for us to use
and recommend the REST API to be honest. Depending on how the metadata
field was added (or edited) the language could be any number of weird
values.
What this says to me is that the language attribute should have a
controlled vocabulary. One should not be *allowed* to enter weird values.
At the very least it should be required to match
/^[[:lower:]]{2}(_[[:upper:]]{2})?$/
(I'm sorry to say that I couldn't find a standard locale name for
"unknown", in case some researcher returns from the bush with literature in
a previously unknown (and thus not yet standardized) language.)
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
