Hi, I'm writing this email to get help on about which approach should i use in order to import data from an internal academic system.
First, let me introduce the situation; I'm an intern at my university and i work mainly with our OJS and VuFind systems, i recently started messing around with DSpace because my boss asked me to give it a look as we're constantly adapting the systems to fit our use [like migrating things from/to ojs, theme'ing vufind...] and we need some changes in our dspace inplementation. I study computer engineering so i have a nice background in the area in general, i'm saying this because i know there are a lot of people who manages dspace which are more from an editorial area. The internal academic system: We use here a *locally* developed academic system, which is *closed source* AFAIK (i don't mean to talk about this, but yeah i know ¬¬), it manages various things from the university and its campus, like grades and etc. This system is also used to register some academic documents like masterthesis and doctoratethesis, so is pretty much the fields that DSpace indexes, like authors, date, type... PS.: The motivation to do this import is to reutilize this fields, not having to enter the thesis metadata again, we just import it from the academic system. The Problem: I was told that we have now an oportunity to ask for the developers to implement something which we may use to harvest this data from our academic system, but i don't have enough experience with dspace to be certain that i'm choosing the best aproach and i think i will have to give them a pretty precise TODO list. What do I need: I need to be able to harvest SOME of this academic stuff periodicaly, there are some types of material that we want to index in Dspace and others not. I believe this separation could be made by either the harvester side (choosing some sorte of tags to import) or by the harvested side (only exposing what's chosen). My boss told me that a solution like making the academic system export some sort of xml file and importing it on DSpace would be fine, and we can chose what to export on the "harvested' side [that is, the academic system]. I understand that this approach requires that i chose some export format accepted by dspace that better fills my needs, something like using QDC. I also thought of something like exposing an OAI-PMH interface from the academic system and making DSpace harvest only what i need (again, by filtering by some tag), and having the possibility of automating the proccess. Can anybody give me some ideias, use case, or anything that i might read to project this import/export dynamic? Samuel Henrique O. P. [samueloph] -- 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.
