Hi Monika, First, i'm sorry for taking so long to reply, i've got to swtich priorities here and now i'm back to this problem.
I am not clear how much human involvement you think you need in the > process. > > Step 1 ) export to dublin core in a way that DSPACE can import from > directories > Step 2) ??? > Step 3) import > > do you want a person to review the exported data to make decisions about > whether to import or not, whether to fix up metadata , and to decide which > collections items should be assigned to ? If the answer is yes your job > will be difficult. > To answer the last question, kind of yes, i'm gonna try to give a better explanation of what is my problem: Let's say somebody is graduating (or getting a masther or doctorate degree), this person has to do some academic work (tcc, thesis...), this work is firstly submitted in our academic system with, by "submitted" i mean that a lot of the metadata is being submitted, like: author names, title, description, type... IF this work is approved (example:the person graduates)[1], we then *have[2]* to pass it to DSpace as a not finished[3] submission because we have to add some fields that won't come from the academic system, like: license, author curriculum (like orcid, but we use one called lattes), the file itself (pdf) and so on, the person that will copy the metadata from the academic system and add its missing metadata will be someone with a submitter role for its collection, and after this person finishes it, some reviewer[4] will have to accept the submission, finally publishing it. Considering this is an all time ongoing process, you can see every attempt to automate it would be great. Now, what i want to do is the following, since we can't ask for an OAI interface yet: The academic system to have a button on this record view page that says something like "export metadata", and it will generate a file containing all the possible metadata used by Dspace, ready for import; The person that is used to manually copy the metadata will access the academic system, download it and import to DSpace, using the WebUI as a non-admin user (altough as a submitter for this collection), as a non finished submission; This same person will now fulfill the missing fields, upload the pdf, accept the license, simplifying, this person will finish the submission, passing the ball to a reviewer whom will publish the submission. We have an opportunity on the next few days of asking for the manager of this academic system to implement this, at the same time aiming for an OAI interface on the future (they won't do it now). So i need to: 1) Define a metadata format that the academic system will follow to export this data. 2) Find a way in which a non-admin DSpace user can import this metadata as a non finished submission. I need help with both 1) and 2) For 2 i found this https://wiki.duraspace.org/display/DSDOC5x/Importing+and+Exporting+Items+via+Simple+Archive+Format#ImportingandExportingItemsviaSimpleArchiveFormat-UIBatchImport(JSPUI) Which says only admin users can import data and only mentions batch import, i believe i would need the basic "import metadata" option above the batch one. For 1 i found some info on the DSpace wiki suggesting that i may use DC Metadata for importation. Every comment regarding this problem is highly appreciated, thanks! If i wasn't clear about anything, please point out and i will happily try to clarify it. [1]When it is approved, it's made within the academic system, so there is a way of identifying only those records we need from the academic system. [2]We have to, but what is really made is that one person manually copies the data showed on the academic system, so from this person's POV is just a normal submission. [3]By "not finished" i mean that this submission is still pending to the submitter and is not available for review yet (no license accepted yet, for example). [4]This comes from the collection workflow setting, as i understood; someone submits, another one review, and the review process publishes. The separation of submitters and reviewers is given by grouping users and setting their permissions for wanted collections. Samuel Henrique O. P. [samueloph] 2016-05-13 12:26 GMT-03:00 Monika C. Mevenkamp <[email protected]>: > You are right of cause > > I am not clear how much human involvement you think you need in the > process. > > Step 1 ) export to dublin core in a way that DSPACE can import from > directories > Step 2) ??? > Step 3) import > > do you want a person to review the exported data to make decisions about > whether to import or not, whether to fix up metadata , and to decide which > collections items should be assigned to ? If the answer is yes your job > will be difficult. > > If the answer is no , along with we’ll generate Dublin core in batches > that match collections - you could ‘simply' write a command line scripts, > that > creates the collections file by deriving it from the ‘batch info’ > import the items > marks the batch as imported > Then run the script as a cronjob so it picks up whatever has been exported > in step 1. > > Monika > > — > Monika Mevenkamp > Digital Repository Infrastructure Developer > Princeton University > Phone: 609-258-4161 > Skype: mo-meven > > On May 13, 2016, at 10:58 AM, SamuelOPH <[email protected]> wrote: > > Hi Monika > > When you say non -admin - are you asking for a way to do this through the >> web UI ? >> > > Not only using the web, because the procedure of importing throughthe UI > showed here[1] explicit the need to use the "Administer" option in step2, i > believe only those who have total admin permissions on dspace can do that, > please correct me if i'm wrong, as i may be wrongly assuming how the > permission systems work on DSpace. > > If you envision a process where users will log into DSPACE - why not >> import everything into the workflow of the relevant collection and then >> have users approve or reject submissions ? >> > > I'm not quite sure i understood what you suggest. Are you suggesting that > the admin of dspace do one import with all the works that will need to be > migrated and them the users responsible for that collections will accept or > reject them? If so, that is not possible because this will be a constant > process, we have to constantly import data from our academic system. I know > that obviously OAI-PMH would be better fit for this case, as its automatic, > but there's a high chance that we will need to go for this > burocratic-but-better-than-nothing way for now. > > Thanks for your answer > > [1] > https://wiki.duraspace.org/display/DSDOC5x/Importing+and+Exporting+Items+via+Simple+Archive+Format > > Samuel Henrique O. P. [samueloph] > > 2016-05-13 11:39 GMT-03:00 Monika C. Mevenkamp <[email protected]>: > >> When you say non -admin - are you asking for a way to do this through the >> web UI ? >> >> If you envision a process where users will log into DSPACE - why not >> import everything into the workflow of the relevant collection and then >> have users approve or reject submissions ? >> >> Monika >> >> >> — >> Monika Mevenkamp >> Digital Repository Infrastructure Developer >> Princeton University >> Phone: 609-258-4161 >> Skype: mo-meven >> >> On May 12, 2016, at 3:00 PM, SamuelOPH <[email protected]> wrote: >> >> Thanks for your suggestion Stuart. >> >> We decided that we will implement OAI-PMH later and first we will make >> the academic system export the itens we want to add to Dspace using some >> format like DC. >> >> I would like to know how is the import/export procedure on DSpace, is >> there a place where users with granted permissions (but not admin) can >> upload files to be imported on Dspace? >> >> I found this page[1] which explains what i believe is what i'm aiming >> right now, is there a way a non-admin user can import itens? >> >> [1] >> https://wiki.duraspace.org/display/DSDOC5x/Importing+and+Exporting+Items+via+Simple+Archive+Format >> >> Samuel Henrique O. P. [samueloph] >> >> 2016-05-02 17:45 GMT-03:00 Stuart A. Yeates <[email protected]>: >> >>> You should seriously consider asking the developers to implement an OAI >>> interface https://www.openarchives.org/OAI/openarchivesprotocol.html >>> >>> There are a number of toolkits with various functionality and technical >>> platforms at https://www.openarchives.org/pmh/tools/tools.php which >>> means the developers may not have to do all the work from scratch. >>> >>> There are also some convenient validators. >>> >>> cheers >>> stuart >>> >>> -- >>> ...let us be heard from red core to black sky >>> >>> On Tue, May 3, 2016 at 5:28 AM, SamuelOPH <[email protected]> wrote: >>> >>>> 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. >>>> >>> >>> >> >> -- >> 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. >> >> >> > > -- 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.
