Hi Darren,
to be very clear: are you looking for a way to clean up the current errors,
or just interested in prevention for new ones? In terms of prevention, it
might help if you develop an auto-complete feature that tries to match
anything a user is entering in a particular metadata field, with those
values that are already stored for that field in archived items.
Referring back to your example, this would mean that if someone starts
typing "AB..." he or she would get suggestions for ways in which someone
else has already entered values starting with "AB" for that specific
metadata field.
To deal with errors that already made it into your metadata, here are two
suggestions, a free one, and a commercial add-on module from @mire:
- Since DSpace 1.6 you can export metadata into spreadsheets on a
per-collection basis. So download the metadata in a spreadsheet, clean it
up, and re-upload to see the changes get into effect. For the "clean up"
part, you can go at it with your spreadsheet editor but you might want to
look at Google Refine <http://code.google.com/p/google-refine/>. It's
really awesome at detecting "similar" values and grouping them together.
- Our Metadata quality module <http://atmire.com/website/?q=modules/mqm> has
functionality for performing batch edits straight from the DSpace web UI
and merging duplicates.
cheers,
Bram
--
[image: logo]
*Bram Luyten* *@mire*
*2888 Loker Avenue East, Suite 305, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
<http://www.atmire.com/>www.atmire.com<http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml>
On Wed, Aug 29, 2012 at 8:32 PM, DSpace @ Lyncode <[email protected]>wrote:
> Hi,
>
> i can only think of implementing an Authority Control for that.
> Anyway, deposit workflow is meant to accomplish that task
> (validate/correct metadata values).
>
> On 29 August 2012 16:22, Darren Arsenault <[email protected]>wrote:
>
>> I posted this a week ago and no one has responded yet, so I'm trying
>> again:
>>
>> "For input fields where it is not possible (or practical) to implement
>> controlled vocabularies or drop down lists, is there a less
>> labour-intensive way of preventing data entry errors? For example: The
>> author of several documents is "ABC Statistics Inc.", but each document is
>> added by a different ePerson,and each of these people makes a spelling
>> error when filling out the AUTHOR field, so these items appear to have
>> different authors. ("ABC Statisitcs, Inc.", "ABC Statistics, Inc", "ABC
>> Statistics", etc.).
>>
>> Originally I thought that this would be a minor issue, easily correctable
>> through raw SQL queries to update the offending fields. Unfortunately, my
>> estimates as to the number of mistakes that would be made has proven to be
>> extremely conservative. I do not want to be responsible for correcting so
>> many entries myself, nor do I want to reject so many entries asking users
>> to match the AUTHOR name that already exists."
>>
>>
>>
>> Does anyone have any ideas?
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> DSpace-tech mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>>
>
>
>
> --
> Thanks,
> DSpace Department
> *Lyncode*: Official
> website<http://www.google.com/url?q=http%3A%2F%2Fwww.lyncode.com%2F&sa=D&sntz=1&usg=AFrqEzdV8iS6rMxflxnn138XReuRfUG3OQ>
>
> [image: Follow us on
> Facebook]<http://www.google.com/url?q=http%3A%2F%2Ftwitter.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzeDuT3ZqMW5uVIA8AoxtTtAeiCX3Q>
> <http://www.google.com/url?q=http%3A%2F%2Fwww.facebook.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzcWXjHa3gKBGLsNVxktapxkiWDnww>
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
