Tech List

[index] [prev] [next] [options] [help]
See the Mailing Lists Page for how to subscribe and unsubscribe.

eprints_tech messages

Please note: this page shows emails that have been sent to the eprints_tech mailing list. Some of these may be spam emails we have failed to filter.

[EP-tech] Re: Subject conversion

From: Andrea Wiggins <awiggins AT syr.edu>
Date: Wed, 5 Nov 2008 20:12:17 -0500


Threading: [EP-tech] Subject conversion from julian.treadwell AT jcu.edu.au
      • This Message

http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** EPrints community wiki - http://wiki.eprints.org/

On Oct 26, 2008, at 9:35 PM, Julian Treadwell wrote:

> *** http://www.eprints.org/tech.php/id/%3C49051AFF.3060307%40jcu.edu.au%3E
> *** EPrints community wiki - http://wiki.eprints.org/
>
> We in Australian Universities have recently been instructed by the  
> Government to replace all our research classification codes (ePrints  
> subjects) with new ones.  I have a one-to-one mapping table and at  
> first thought that a search-and-replace in the subject tables might  
> be enough.  But of course it's not, because the descriptions have  
> also changed, which would make the subject__index and __rindex data  
> incorrect.
>
> What would be the best approach to this problem?  How about doing a  
> search-and-replace in the subject and eprints-subject tables,  
> exporting the subjects as xml via export and re-importing them via  
> import_subjects?
>
> Any advice much appreciated.  We're on version 3.05 (Puffin).
>
> Thanks,
>
> Julian
>
> ------------------------------------------------------------------
> Julian Treadwell
> Systems Administrator
> Eddie Koiki Mabo Library
> James Cook University	| Email: julian.treadwell AT jcu.edu.au  
> Townsville		| Ph +61 7 4781 6538
> Queensland 4811		| Fax +61 7 4781 5886
> ------------------------------------------------------------------
>


I've recently migrated an ePrints subject hierarchy, which was  
fortunately not much populated at the time. I more or less deleted the  
bulk of the original hierarchy and rebuilt it via the gui, which was  
not an ideal process for a number of reasons - clearly impractical for  
a large classification system. For the few eprints that had subjects  
assigned to them, I ended up cleaning up afterwards with a series of  
SQL queries, e.g.,

update eprint_subjects set subjects='community_context' where  
subjects=10;
update eprint_subjects set subjects='cultural' where subjects=843;

Hope that helps,

Andrea


Andrea Wiggins
PhD Student, School of Information Studies
Syracuse University

337 Hinds Hall
Syracuse, NY 13244
awiggins AT syr.edu
www.andreawiggins.com


[index] [prev] [next] [options] [help]