[dspace-tech] Re: ant fresh_install error "key for add operation must be defined "

2017-11-14 Thread Feleke Zerihun
Open the following directory C:\dspace-6.2-src-release\dspace\target\dspace-installer open build file in your editer and make scroll down and get line 792 and failonerror="yes" chnge into failonerror="no" -- You received this message because you are subscribed to the Google Groups "DSpace

[dspace-tech] Data Dictionary and structure of the database

2017-11-14 Thread Freddy Guerrero
Dear friends, please your help where I can find the structure of the database (tables) and the data dictionary of dspace? Regards Freddy -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop

[dspace-tech] Re: [Dspace-tech] OAI Harvesting Issues with Geonetwork Sites

2017-11-14 Thread Luis Avalos
Hi Robert, I have some troubles very similar to what you had. So, how did you solve the problem...Now i´m using dspace version 5.5 trying to harvest 3 different geonetwork versions: 3.2.2 , 3.2.1 and 3.2.0 Try after try I reduced options to harvest geographic metadata using Dspace, so this is

[dspace-tech] initial questions step

2017-11-14 Thread Graham Faulkner
Hi there, [We're running DSpace 5.5 XMLUI Mirage2 on Linux.] Re: the Initial Questions Step, it seems like there is only one set of questions that can optionally be used for any submission workflow. Is there a way to have a custom set of questions that is tailored for a workflow? Or would it

[dspace-tech] LDAPAuthentication - can't create ePerson at DEBUG

2017-11-14 Thread Michael White
Hi, DSpace v6.2, JSPUI . . . I've been working to set up (hierarchical) LDAP based authentication on my DSpace v6.2 DEV system but I'm having problems getting the system to auto-create an ePerson record for new users when the log level is set to DEBUG. In this case, the

Re: [dspace-tech] SwordV2 servicedocument not found

2017-11-14 Thread Claudia Jürgen
Hello, sorry that was not right, should have read more carefully or looked at our installation "# In the event that you are not deploying DSpace as the ROOT # application in the servlet container, this will generate # incorrect URLs, and you should override the functionality # by specifying in

Re: [dspace-tech] SwordV2 servicedocument not found

2017-11-14 Thread Claudia Jürgen
Hello, if you are not deploying dspace as the root application, you got to specify the paths in swordv2-server.cfg. So you got dspace.url = https://somedomain.de/xmlui then you got to use this in the sword configuration like servicedocument.url = https://somedomain.de/xmlui/servicedocument