On Wed, Apr 20, 2016 at 4:44 PM, Mark H. Wood <[email protected]> wrote:
> On Wed, Apr 20, 2016 at 09:05:56AM -0500, Tim Donohue wrote: > > In DSpace, all metadata values have a "Language" column associated with > > them. Often times, this "Language" value is either defaults to not being > > set, or to your specified default (e.g. "en_US" , US English). However, > > in some scenarios (usually either a bulk data load or migration), the > > "Language" value might be accidentally set to an empty value (e.g. a > > single space or empty string). That's what causes the seemingly > > duplicate field names. > > Is there any use case for a text_language value of an empty or blank > string? Should we not convert such values to null values in the > business logic layer on ingestion, and remove this puzzle? > No, there isn't. We should ;) Moreover, we should not generate such a duality in the first place, which requires us to check what each of our various import methods does. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- 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.
