[dspace-tech] Poor indexing performance after upgrading from DSpace 4.x to DSpace 6.0

2016-12-08 Thread Franky Cheung 
Hi~ We are users of DSpace 4.x for two years, and recently we need to 
migrate our server. After rsync the files and restore of the database to 
new server, we followed the procedure in the guide to upgrade the DSpace to 
6.0. However, the indexing performance was terrible. It took nearly 3 hours 
for indexing 20,000 records! I spent hours for tuning the tomcat (allocate 
5GB ram to both tomcat and JAVA command line, increase memory for 
PostgreSQL, searching for best GC settings, change merge factor in Solr, 
etc.) The performance did slightly improve, but it was still quite far from 
what we had in DSpace 4.x. 

Finally, we decided to upgrade to an older version DSpace 5.6. We rsync the 
4.x version from the old server to new server again and upgraded to 5.6. We 
followed the same procedure without changing the tomcat settings. The 
indexing performance is great as DSpace 4.x, within 30mins, 53xxx records 
have been indexed.

Since the hardware config and the tomcat settings are the same, I guess 
there are obviously some problems with DSpace 6.0, or the upgrade process 
from 4.x to 6.0. Hope this can help DSpace 6.0 to be better.

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Dspace-CRIS Deduplication: the merge tool error

2016-12-08 Thread Yen-Tang Chen 
Dear all

I test to Deduplication function in the Dspace-CRIS-5.6.1 that I start two 
same submission. 
I use Compare function => error
(Deduplicationt_he merge tool.png)
(Deduplicationt_he merge tool_001.png)

I don't know what the problem is error
I'm missing a step?


dspace.log message

2016-12-09 10:35:01,275 WARN  
org.dspace.app.webui.servlet.InternalErrorServlet @ 
:session_id=C848406B638AC7632F36A10836B1E809:internal_error:-- URL Was: 
http://140.112.113.49:8080/jspui/tools/duplicate
-- Method: POST
-- Parameters were:
-- mergeByUser: "false"
-- submittargetchoice: "Compare"
-- itemstomerge: "62"
-- target: "61"
-- rule: "0"
-- scope: "0"
-- signatureType: "null"

java.lang.ArrayIndexOutOfBoundsException: 3
at 
org.dspace.content.DSpaceObject.getMetadataByMetadataString(DSpaceObject.java:635)
at 
org.dspace.content.DSpaceObject.getMetadataValueInDCFormat(DSpaceObject.java:1403)
at 
org.dspace.content.DSpaceObject$$FastClassByCGLIB$$5da9b798.invoke()
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at 
org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at 
org.dspace.app.cris.integration.CrisItemWrapper.invoke(CrisItemWrapper.java:107)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at 
org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
at 
org.dspace.content.Item$$EnhancerByCGLIB$$d63e1dbd.getMetadataValueInDCFormat()
at 
org.dspace.app.webui.cris.servlet.DuplicateCheckerServlet.loadTarget(DuplicateCheckerServlet.java:891)
at 
org.dspace.app.webui.cris.servlet.DuplicateCheckerServlet.doDSPost(DuplicateCheckerServlet.java:520)
at 
org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:115)
at 
org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at 
org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnlyFilter.java:66)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at 
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at 
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:528)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1100)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:687)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1520)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1476)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)




Sincerely yours, Yen-Tang Chen

-- 
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 dspace-tech+unsubsc

[dspace-tech] Re: Running Jetty as different user, problems uploading file

2016-12-08 Thread David Brian Holt 
OK, I changed the user that runs Jetty (by editing the jetty script in the 
init.d directory and changing the JETTY_USER to "postgres", the same user I 
created when I installed).  Now I'm getting a different error when I upload.




Any suggestions?

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Running Jetty as different user, problems uploading file

2016-12-08 Thread David Brian Holt 
I'm a noob so forgive me if this is a stupid question. 

I'm getting an error when trying to attach a file to a Dspace item record. 
 After reading some previous posts, I think it is caused by a permissions 
error but I'm lost as to how I fix it.  

This is the error stack:

Java stacktrace: java.io.IOException: No such file or directory at 
java.io.UnixFileSystem.createFileExclusively(Native Method) at 
java.io.File.createNewFile(File.java:1012) at 
org.dspace.storage.bitstore.DSBitStoreService.put(DSBitStoreService.java:123) 
at 
org.dspace.storage.bitstore.BitstreamStorageServiceImpl.store(BitstreamStorageServiceImpl.java:107)
 
at 
org.dspace.content.BitstreamServiceImpl.create(BitstreamServiceImpl.java:101) 
at 
org.dspace.content.BitstreamServiceImpl.create(BitstreamServiceImpl.java:120) 
at 
org.dspace.content.ItemServiceImpl.createSingleBitstream(ItemServiceImpl.java:331)
 
at org.dspace.submit.step.UploadStep.processUploadFile(UploadStep.java:547) 
at org.dspace.submit.step.UploadStep.doProcessing(UploadStep.java:151) at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
at java.lang.reflect.Method.invoke(Method.java:498) at 
org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155) at 
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243) at 
org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237) at 
org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394) at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162) 
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393) 
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834) 
at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160) 
at org.mozilla.javascript.Context.call(Context.java:538) at 
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833) 
at 
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1803) 
at 
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:698)
 
at 
org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:94)
 
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
 
at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
 
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 
at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:82)
 
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
 
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
 
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239)
 
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:186)
 
at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(TreeProcessor.java:260)
 
at 
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:107)
 
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 
at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:87)
 
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
 
at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
 
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
 
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
 
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239)
 
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:186)
 
at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(TreeProcessor.java:260)
 
at 
org.apache.cocoon.components.tre

[dspace-tech] xmlui.bitstream.mods / xmlui.bitstream.mets

2016-12-08 Thread Terry Brady 
Re-posting with a meaningful subject line

On Thursday, December 8, 2016 at 1:17:55 PM UTC-8, Terry Brady wrote:
>
> The XMLUI Configuration Reference Page on the Wiki 
> 
>  mentions 
> 2 settings.
>
>- xmlui.bitstream.mods
>- xmlui.bitstream.mets
>
> How does a DSpace instance behave when these settings are in use?
>
> Do you know of examples where these settings are active?
>
> Thanks, Terry
>
> -- 
> Terry Brady
> Applications Programmer Analyst
> Georgetown University Library Information Technology
> http://georgetown-university-libraries.github.io/ 
> 
> 425-298-5498 (Seattle, WA)
>

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] xm

2016-12-08 Thread Terry Brady 
The XMLUI Configuration Reference Page on the Wiki

mentions
2 settings.

   - xmlui.bitstream.mods
   - xmlui.bitstream.mets

How does a DSpace instance behave when these settings are in use?

Do you know of examples where these settings are active?

Thanks, Terry

-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
http://georgetown-university-libraries.github.io/

425-298-5498 (Seattle, WA)

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Select Collection step performance very slow in DSpace 6.x

2016-12-08 Thread wltantzen 
I agree -- I have just run a test of v5.6 on the same machine just to 
compare apples with apples.  It's not hardware or configuration.  I will 
provide you with some numbers from what I have learned shortly.

Cheers!
Bill

On Wednesday, December 7, 2016 at 2:59:11 PM UTC-6, Tom Desair (Atmire) 
wrote:
>
> This is indeed probably not a hardware issue but related to the new 
> database abstraction layer (Hibernate), similar to 
> https://jira.duraspace.org/browse/DS-3004
>
> Can someone share the profiling report of a case where it runs really slow?
>
>  
> [image: logo] Tom Desair
> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
> Esperantolaan 4, Heverlee 3001, Belgium
> www.atmire.com 
> 
>
> 2016-12-02 16:11 GMT+01:00 >:
>
>> I have similar specs, except for ssd drives:
>>
>> 8 CPUs, GenuineIntel, 2299.998 MHz
>> 32 GB with -Xmx16384m
>> tomcat 8,0.33
>> postgresql-9.5.1
>>
>> Like I said, this same machine cruised nicely with v5.6.  Page loads are 
>> subjectively slower across the board, but the Submission page load time is 
>> an upgrade killer.
>>
>> On Friday, December 2, 2016 at 4:08:02 AM UTC-6, Joan Caparros wrote:
>>>
>>> We are experiencing the something similar but in all our repository 
>>> (except the home page), almost all pages in DSpace 6x takes between 6s to 
>>> 60seconds, we have tried to increase the memory of the tomcat, changed the 
>>> SO (Centos7 to Ubuntu), upgrading tomcat (8.0.5 to 8.5), giving more cpus, 
>>> changing data to ssd hard drive... all without a signigicant improvements 
>>> of performance.
>>>
>>> Our configs are:
>>>
>>> Vcpus : 8 (GenuineIntel  2099.998MHz)
>>>
>>> Tomcat (8.5.8) config:  -Xmx4072M -Xms512M -XX:PermSize=256M 
>>> -XX:MaxPermSize=512m
>>>
>>> Items: arroung 120k
>>>
>>> Now we have in production DSpace 3_x and this situation is preventing us 
>>> from upgrading also.
>>>
>>> Bests
>>>
>>> Joan 
>>> El 01/12/16 a les 22:15, wlta...@gmail.com ha escrit:
>>>
>>> In DSpace 6x, it takes an intolerable 10 minutes (!!!) to populate the 
>>> Select Collection drop-down in my instance when logging in as a regular 
>>> user as opposed to an administrator.  
>>>
>>> I can add hardware details if anybody is interested, but I'm pretty sure 
>>> it's not the problem -- this is a beefy machine that hummed along nicely 
>>> with version 5.x...
>>>
>>> We have a little over 1000 collections in our repository, and we use 
>>> shibboleth for authentication so findAuthorizedPerformanceOptimize is set 
>>> to it's default of false.
>>>
>>> Some rudimentary profiling suggests that the isAdmin() call in 
>>> authorize() is the bottleneck.  In a recent test (pretty typical), the 
>>> findAuthorized() function takes 704,040 ms to return.  The time spent in 
>>> the isAdmin() call amounts to 590,691 ms, or about 83% of the time.  
>>> Another bottleneck within this bottleneck is the recursive call to 
>>> isAdmin(parent collection) -- about 400,000 ms.  Clearly there is a lot of 
>>> waste in this call because many many collections will be tested over and 
>>> over.  In our case, we have a single community that is the ancestor of 
>>> every community/collection, and isAdmin() winds up being called against it 
>>> 1012 times -- same as the number of collections in the repository -- and 
>>> 1011 of them are redundant.
>>>
>>> As a further test, I have short-circuited isAdmin() to return false 
>>> immediately.  The results in the rendering of the drop-down in about 94,000 
>>> msec.  Still way too long, but a drastic improvement.
>>>
>>> When logging in as an administrator, isAdmin() returns rather quickly 
>>> and the list is populated much quicker as well.  But for the everyday user, 
>>> the performance is a big red light preventing us from upgrading.
>>>
>>> Sorry, this is simply stating the problem with no solution.  But has 
>>> anybody else with a similarly sized repository experienced this slow down?
>>>
>>> Regards,
>>> Bill
>>>
>>>
>>> -- 
>>> 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 dspace-tech...@googlegroups.com.
>>> To post to this group, send email to dspac...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>> -- 
>>> .
>>>
>>> Joan Caparrós
>>> Tècnic de Projectes
>>> Consorci de Serveis Universitaris de Catalunya (CSUC)
>>>
>>> Gran Capità, 2 (Edifici Nexus)•08034 Barcelona
>>> T.93 551 6204•F.93 205 6979•joan.c...@csuc.catwww.csuc.cat •Twitter 
>>> @CSUC_info•Facebook•Linkedin
>>> Subscriu-te al butlletí; (www.csuc.cat/butlleti)
>>> ..

[dspace-tech] Re: the dspce is not running

2016-12-08 Thread Null Null 
help me?

18 Kasım 2016 Cuma 16:44:08 UTC+3 tarihinde Null Null yazdı:
>
> hi.
> I did the installation. I did not get any errors. The anchors are not 
> working now. 
>
> error
>
> FAIL - Application at context path /jspui could not be started
>
>  
> 
>
> FAIL - Application at context path /xmlui could not be started
>
>

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Git Rebase Issue

2016-12-08 Thread Terry Brady 
Ivan,

Thanks for the instructions.  I have added them to my git cheat sheet.

I am not sure why my original rebase created this error.  I am glad to see
that I was able to repair 3 of my 4 branches.

I concur with Hardy that it could be useful to have a set of useful git
recipes on the DSpace wiki.

Terry

On Thu, Dec 8, 2016 at 6:02 AM, Hardy Pottinger 
wrote:

> Helix84, that is a fantastic write-up! Would you consider adding a version
> of it to the DSpace wiki in the section about how to use Git? I have always
> wondered what might have happened when I have seen thousands of commits not
> my own show up in a pull request. So far the only thing I've found to work
> in this situation is to "take a Mulligan" and re-do the branch (either
> manually, or via a "cherry-pluck" (warning, not an actual command, just a
> descriptive word, coined by Peter Dietz). This poster [1] has been helpful
> to me. But, I feel better knowing that someone can explain what *probably*
> went wrong, and that there *are* commands you can run to *put it right*
> without resorting to the Mulligan.
>
> Thanks!
>
> --Hardy
>
> [1] http://justinhileman.info/article/git-pretty/git-pretty.pdf
>
> On Thu, Dec 8, 2016 at 3:03 AM, helix84  wrote:
>
>> The last command should have been just:
>>
>> git push terrywbrady ds3282 --force
>>
>>
>> Regards,
>> ~~helix84
>>
>> Compulsory reading: DSpace Mailing List Etiquette
>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>
>> --
>> 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 dspace-tech+unsubscr...@googlegroups.com.
>> To post to this group, send email to dspace-tech@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>


-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
http://georgetown-university-libraries.github.io/

425-298-5498 (Seattle, WA)

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: [dspace-community] Mirage 2 not working after upgrading to DSpace 6.0

2016-12-08 Thread Pedro Amorim 
Hello Yongming,

Check this topic on DSpace Tech:
https://groups.google.com/forum/#!searchin/dspace-tech/pedro$20amorim%7Csort:relevance/dspace-tech/2qQvNL2KOB8/0HxajN6zAQAJ

You should use maven 3.3.9.
Also, check the build process on the Mirage 2 Local Customizations
component, the overall DSpace build might be successfull but actually fail
at Mirage 2. In my case, bower wasnt being installed correctly and Î had to
create the directories manually.

Good luck,

Pedro Amorim

2016-12-08 13:52 GMT-01:00 Wang, Yongming :

> Dear all,
>
> I have just upgraded our DSpace 5.1 to 6.0.
>
> In DSpace 5.1 we used jspui. In 6.1 we decide to use xmlui.  I followed
> the upgrade/install instruction to include and enable Mirage 2 by the
> following steps:
>
> 1. edit /local/home/dspace/dspace-6.0-release/dspace/config/xmlui.xconf
> change
> 
> to
> 
>
> 2. [dspace-source]/dspace]$ mvn -U clean package -Dmirage2.on=true
>
> The build process is success without any error.
>
> But when I access the homepage of our DSpace, the Mirage 2 is obviously
> not displaying right. It looked like the template is somehow broken. And I
> saw this message on the screen:
>
> "JavaScript is disabled for your browser. Some features of this site may
> not work without it."
>
> My browser's javascript IS enabled!
>
>
> Does anyone know what the reason is and how to solve this issue?
>
>
> Thank you very much.
>
>
>
>
> Yongming
>
>
>
> --
> Yongming Wang
> Systems Librarian/Associate Professor
> The College of New Jersey
> tel: 609-771-3337 <(609)%20771-3337>
> email: wan...@tcnj.edu
>
> --
> You received this message because you are subscribed to the Google Groups
> "DSpace Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-community+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-commun...@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-community.
> 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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Question about DSpace code and version control of local mods

2016-12-08 Thread Luiz dos Santos 
Thank you Tom!

Luiz Claudio Santos
http://luizclaudiosantos.me/

On Thu, Dec 8, 2016 at 9:11 AM, Mark Wood  wrote:

> We used to keep our local DSpace in SVN alongside a copy of stock code, to
> make it easy to keep our mod.s updated.  Some time ago we switched to git,
> and now keep local DSpace and stock in a local instance of GitHub
> Enterprise.  I find SCM tools to be much easier to work with than the
> overlay stuff.
>
> --
> 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 dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> 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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Question about DSpace code and version control of local mods

2016-12-08 Thread George Kozak 
Thank you, everyone for your suggestions and comments!
George Kozak
Cornell University

On Wed, Dec 7, 2016 at 5:15 PM, Luiz dos Santos  wrote:

> Sure, let me reformulate my question, what is the difference between the
> build configuration in the "development version" and "release version", for
> example, I got that the configuration of the maven "license-maven-plugin"
> is different in the pom.xml is different, it makes sense, because in the
> end of the day the files are not there, in the release version, so there is
> less to check, but I wonder where else there is a difference (maybe
> assembly plugin)?
>
> Sorry George, out of topic, but I am curious about it, and I guess your
> question was already answered, right?
>
> Thanks
> Luiz Claudio Santos
> http://luizclaudiosantos.me/
>
> On Wed, Dec 7, 2016 at 4:38 PM, Tom Desair  wrote:
>
>> No you cannot just delete them. You have to start from the correct format.
>>
>> DSpace is always released under two formats: a "release-src" archive that
>> contains the full DSpace source as it can be found on Github and a
>> "release" archive that only contains the configuration files and some
>> folders where you can put Java customisations. The "release" version will
>> download the (compiled) DSpace source code at build time from Maven.
>>
>> The example repository uses this "release" version. For DSpace 6, you can
>> download that version here https://github.com/DSpace
>> /DSpace/releases/download/dspace-6.0/dspace-6.0-release.tar.gz (
>> https://github.com/DSpace/DSpace/releases/tag/dspace-6.0)
>>
>>
>> [image: logo] Tom Desair
>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
>> Esperantolaan 4, Heverlee 3001, Belgium
>> www.atmire.com
>> 
>>
>>
>> 2016-12-07 21:31 GMT+01:00 Luiz dos Santos :
>>
>>> Hi Tom,
>>>
>>>   One question, the repository that you add the link there are some
>>> folders missing, such as dspace-jspui, dspace-api, dspace-oai... How did
>>> you do that? Just delete it? Do you add these as dependencies somewhere
>>> else?
>>>
>>> Thanks in advance
>>> Luiz Claudio Santos
>>> http://luizclaudiosantos.me/
>>>
>>> On Wed, Dec 7, 2016 at 3:19 PM, Tom Desair 
>>> wrote:
>>>
 Hi all,

 The general approach we use, is to download the release version of
 DSpace (note: note the src-release version) which is very small and push
 this to a Git repository. Then we save all our customisations in the
 relevant module directory. This process is described here:
 https://wiki.duraspace.org/display/DSDOC5x/Advanced+Customisation

 An open source example of a highly customised DSpace using this
 technique can be found here: https://github.com/milie
 uinfo/dspace54-atmire/tree/java-DEV

 Best regards,
 Tom


 [image: logo] Tom Desair
 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
 Esperantolaan 4, Heverlee 3001, Belgium
 www.atmire.com
 

 2016-12-07 20:45 GMT+01:00 Alan Orth :

> Hi, George.
>
> You should absolutely be using a git-based workflow. First, git is fun
> and cool and much better in every way than CVS/SVN, but it's also the
> official version control of the DSpace project itself since about 2014
> or so. This is important for cherry-picking patches, rebasing your
> local changes on top of upstream point releases, etc.
>
> Second, GitHub is great. We forked DSpace's DSpace repository there
> and I cherry-pick commits from their branch from time to time, as well
> as rebase on their point releases as I mentioned above. Even though
> I'm basically the only technical one doing DSpace on our team, I make
> *extensive* use of GitHub other features like issues, pull requests,
> and wikis. For example, when a user reports a bug or feature, I create
> an issue to track it, then when I get time to address it I make a pull
> request to my institution's repository from my personal repository.
>
> Here's our repo, where all of our code is (~25 Mirage 2 themes, custom
> input forms, etc):
>
> https://github.com/ilri/DSpace
>
> On Wed, Dec 7, 2016 at 9:34 PM, Luiz dos Santos 
> wrote:
> > Hi,
> >
> >  We have code in github and svn. The svn is old version that
> Atmire
> > folks are updating now. Soon, it's gonna github only, most of the
> code of
> > the code is in a maven repository, as a jar files, only the local
> changes
> > and config file are in the github repository. The developers have
> their own
> > maven profile in the main pom.xml, it helps a lot.
> >
> > Luiz Claudio Santos
> > http://luizclaudiosantos.me/
> >
> > On Wed, Dec 7, 2016 at 2:24 PM, Friesen, Darry

[dspace-tech] Re: SAF and Metadata Export Ordering

2016-12-08 Thread Mark Wood 
It's probably ordered by whatever the DBMS finds convenient.  In that case 
it may not even be consistently ordered as items are added to a 
collection.  A relational query doesn't guarantee any particular order; the 
DBMS is free to arrange and re-arrange its own storage in 
implementation-dependent ways.  I imagine that nobody ever thought of a 
reason to pay the cost of sorting by adding ORDER BY to the query that 
produces the stream of items.

Are you asking out of sheer curiosity, or have you discovered a way in 
which the order of exports can be significant?

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Question about DSpace code and version control of local mods

2016-12-08 Thread Mark Wood 
We used to keep our local DSpace in SVN alongside a copy of stock code, to 
make it easy to keep our mod.s updated.  Some time ago we switched to git, 
and now keep local DSpace and stock in a local instance of GitHub 
Enterprise.  I find SCM tools to be much easier to work with than the 
overlay stuff.

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Tomcat 8 versus Tomcat 7

2016-12-08 Thread Mark Wood 
On my development box I'm currently using Tomcat 8.0 with 5x and 6.  We're 
still on 7.0 in production (5x) but I want to move to 8 when I can find the 
time.

The only issue I can recall is that Tomcat 8's classloader setup is much 
more finicky, and that collides with the way I like to deploy webapp.s.  I 
inject a ready-made database connection pool via JNDI, and if I'm not 
careful to delete the database driver JAR from each DSpace webapp. then 8 
will complain that it can't find the driver (because there's one in 
Tomcat's own classloader, which supplies the pool, and another in the 
webapp's classloader, and they aren't the same 'Class'es even though they 
are loaded from identical files).  I reckon that most sites won't have that 
problem.  When I have some time, I mean to create an option to leave the 
database driver JAR out of the webapps during assembly.

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Git Rebase Issue

2016-12-08 Thread Hardy Pottinger 
Helix84, that is a fantastic write-up! Would you consider adding a version
of it to the DSpace wiki in the section about how to use Git? I have always
wondered what might have happened when I have seen thousands of commits not
my own show up in a pull request. So far the only thing I've found to work
in this situation is to "take a Mulligan" and re-do the branch (either
manually, or via a "cherry-pluck" (warning, not an actual command, just a
descriptive word, coined by Peter Dietz). This poster [1] has been helpful
to me. But, I feel better knowing that someone can explain what *probably*
went wrong, and that there *are* commands you can run to *put it right*
without resorting to the Mulligan.

Thanks!

--Hardy

[1] http://justinhileman.info/article/git-pretty/git-pretty.pdf

On Thu, Dec 8, 2016 at 3:03 AM, helix84  wrote:

> The last command should have been just:
>
> git push terrywbrady ds3282 --force
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
> --
> 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 dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> 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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] E-Prints to Dspace conversion (URGENT)

2016-12-08 Thread Hilton Gibson 
Hi Divya,

Here are the interoperability options:
http://wiki.lib.sun.ac.za/index.php/SUNScholar/Interoperability

Cheers

hg

*Hilton Gibson*
Stellenbosch University Library
*http://orcid.org/-0002-2992-208X
*


On 8 December 2016 at 13:10, Divya Batra  wrote:

> Dear All,
>
> Dspace uses PostgreSQL for database.
>
> We were earlier using Eprints which uses MySQL database.
> We are now shifting to Dspace as document repository.
>
> I want to ask that is there any way we can convert MySQL database to
> PostgreSQL directly so that we can easily import the data as our database
> has more than 4000 records and it will be very time consuming to do
> individual data entry for all the records.
>
> Hoping for a solution.
>
> Thanks & Regards
> Divya
>
> --
> 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 dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> 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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] E-Prints to Dspace conversion (URGENT)

2016-12-08 Thread Divya Batra 
Thanks.
I want to know is it impossible to convert from Eprints to dspace.



On Thu, Dec 8, 2016 at 4:51 PM, helix84  wrote:

> It doesn't work that way at all. It's apples and oranges.
>
> Since you indicated it's urgent and you don't even know how to start,
> I suggest you contact one of the commercial service providers who can
> surely help you:
>
> http://www.dspace.org/service-providers
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
> On Thu, Dec 8, 2016 at 12:10 PM, Divya Batra 
> wrote:
> > Dear All,
> >
> > Dspace uses PostgreSQL for database.
> >
> > We were earlier using Eprints which uses MySQL database.
> > We are now shifting to Dspace as document repository.
> >
> > I want to ask that is there any way we can convert MySQL database to
> > PostgreSQL directly so that we can easily import the data as our database
> > has more than 4000 records and it will be very time consuming to do
> > individual data entry for all the records.
> >
> > Hoping for a solution.
> >
> > Thanks & Regards
> > Divya
> >
> > --
> > 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 dspace-tech+unsubscr...@googlegroups.com.
> > To post to this group, send email to dspace-tech@googlegroups.com.
> > 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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] E-Prints to Dspace conversion (URGENT)

2016-12-08 Thread Claudia Jürgen 

Hello Divya,

DSpace supports several ways to ingest content and there are import
possibilities for documents, structure etc. see
https://wiki.duraspace.org/display/DSDOC6x/Ingesting+Content+and+Metadata
and there is AIP
https://wiki.duraspace.org/display/DSDOC6x/AIP+Backup+and+Restore

EPrints has an export function and the possibility to create export plugins:
https://wiki.eprints.org/w/Create_Export_Plugins

So a possibility would be to create an export from EPrints which matches
one of the import formats from DSpace.

Hope this helps

Claudia Jürgen



Am 08.12.2016 um 12:10 schrieb Divya Batra:

Dear All,

Dspace uses PostgreSQL for database.

We were earlier using Eprints which uses MySQL database.
We are now shifting to Dspace as document repository.

I want to ask that is there any way we can convert MySQL database to
PostgreSQL directly so that we can easily import the data as our database
has more than 4000 records and it will be very time consuming to do
individual data entry for all the records.

Hoping for a solution.

Thanks & Regards
Divya



--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia.juer...@tu-dortmund.de
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.

--
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] E-Prints to Dspace conversion (URGENT)

2016-12-08 Thread helix84 
It doesn't work that way at all. It's apples and oranges.

Since you indicated it's urgent and you don't even know how to start,
I suggest you contact one of the commercial service providers who can
surely help you:

http://www.dspace.org/service-providers


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


On Thu, Dec 8, 2016 at 12:10 PM, Divya Batra  wrote:
> Dear All,
>
> Dspace uses PostgreSQL for database.
>
> We were earlier using Eprints which uses MySQL database.
> We are now shifting to Dspace as document repository.
>
> I want to ask that is there any way we can convert MySQL database to
> PostgreSQL directly so that we can easily import the data as our database
> has more than 4000 records and it will be very time consuming to do
> individual data entry for all the records.
>
> Hoping for a solution.
>
> Thanks & Regards
> Divya
>
> --
> 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 dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> 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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] E-Prints to Dspace conversion (URGENT)

2016-12-08 Thread Divya Batra 
Dear All,

Dspace uses PostgreSQL for database.

We were earlier using Eprints which uses MySQL database.
We are now shifting to Dspace as document repository.

I want to ask that is there any way we can convert MySQL database to
PostgreSQL directly so that we can easily import the data as our database
has more than 4000 records and it will be very time consuming to do
individual data entry for all the records.

Hoping for a solution.

Thanks & Regards
Divya

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] RE: Installing DSpace 6.0 without git : Maven build error

2016-12-08 Thread Devaux Cédric 
Thanks.
(This error occured when installing DSpace 6.0 from Source Release : 
dspace-6.0-src-release.zip, I haven't tested from Binary Release : 
dspace-6.0-release.zip)

Regards,
Cedric


De : Terry Brady [mailto:tw...@georgetown.edu]
Envoyé : mercredi 7 décembre 2016 21:12
À : DSpace Technical Support
Cc : Devaux Cédric
Objet : Re: Installing DSpace 6.0 without git : Maven build error

A ticket has been created in the DSpace proejct to track this issue.

https://jira.duraspace.org/browse/DS-3418

On Monday, December 5, 2016 at 6:39:40 AM UTC-8, Devaux Cédric wrote:
Hello,

When installing DSpace 6.0 ( default theme, not Mirage 2 theme), an error has 
occurred at the step "7.Build the Installation Package : mvn clean package" 
because git is not installed  :
[ERROR] Failed to execute goal 
org.codehaus.mojo:buildnumber-maven-plugin:1.4:create (default) on project 
dspace-api: Cannot get the revision information from the scm repository :
[ERROR] Exception while executing SCM command. Error while executing command. 
Error while executing process. Cannot run program "git"

This error disappears if I remove from [dspace-source]dspace-api\pom.xml, the 
lines about buildnumber-maven-plugin (...) and the installation of 
DSpace 6.0 seems OK.
I haven't investigate the consequences of the removal.
So, Git has to be installed for Dspace 6.0  (XMLUI and JSPUI default theme) or 
buildnumber-maven-plugin has to be removed from pom?

Regards,
Cedric

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Question about DSpace code and version control of local mods

2016-12-08 Thread Tom Desair 
Hi Luiz,

I do not know the exact differences, but high-level we tend to use the
"release version" because:

   - There are less files -> smaller size
   - It will download the compiled DSpace jars at build time so you don't
   have to build them yourself -> faster builds
   - Compared to cloning from the official Github repository, you don't
   have to upload the entire DSpace history to your Git server -> smaller Git
   footprint
   - There is a nice separation between the official DSpace code and your
   own customisations. The repository contains only our own modifications
   (except for the config files).


[image: logo] Tom Desair
250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
Esperantolaan 4, Heverlee 3001, Belgium
www.atmire.com



2016-12-07 23:15 GMT+01:00 Luiz dos Santos :

> Sure, let me reformulate my question, what is the difference between the
> build configuration in the "development version" and "release version", for
> example, I got that the configuration of the maven "license-maven-plugin"
> is different in the pom.xml is different, it makes sense, because in the
> end of the day the files are not there, in the release version, so there is
> less to check, but I wonder where else there is a difference (maybe
> assembly plugin)?
>
> Sorry George, out of topic, but I am curious about it, and I guess your
> question was already answered, right?
>
> Thanks
> Luiz Claudio Santos
> http://luizclaudiosantos.me/
>
> On Wed, Dec 7, 2016 at 4:38 PM, Tom Desair  wrote:
>
>> No you cannot just delete them. You have to start from the correct format.
>>
>> DSpace is always released under two formats: a "release-src" archive that
>> contains the full DSpace source as it can be found on Github and a
>> "release" archive that only contains the configuration files and some
>> folders where you can put Java customisations. The "release" version will
>> download the (compiled) DSpace source code at build time from Maven.
>>
>> The example repository uses this "release" version. For DSpace 6, you can
>> download that version here https://github.com/DSpace
>> /DSpace/releases/download/dspace-6.0/dspace-6.0-release.tar.gz (
>> https://github.com/DSpace/DSpace/releases/tag/dspace-6.0)
>>
>>
>> [image: logo] Tom Desair
>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
>> Esperantolaan 4, Heverlee 3001, Belgium
>> www.atmire.com
>> 
>>
>>
>> 2016-12-07 21:31 GMT+01:00 Luiz dos Santos :
>>
>>> Hi Tom,
>>>
>>>   One question, the repository that you add the link there are some
>>> folders missing, such as dspace-jspui, dspace-api, dspace-oai... How did
>>> you do that? Just delete it? Do you add these as dependencies somewhere
>>> else?
>>>
>>> Thanks in advance
>>> Luiz Claudio Santos
>>> http://luizclaudiosantos.me/
>>>
>>> On Wed, Dec 7, 2016 at 3:19 PM, Tom Desair 
>>> wrote:
>>>
 Hi all,

 The general approach we use, is to download the release version of
 DSpace (note: note the src-release version) which is very small and push
 this to a Git repository. Then we save all our customisations in the
 relevant module directory. This process is described here:
 https://wiki.duraspace.org/display/DSDOC5x/Advanced+Customisation

 An open source example of a highly customised DSpace using this
 technique can be found here: https://github.com/milie
 uinfo/dspace54-atmire/tree/java-DEV

 Best regards,
 Tom


 [image: logo] Tom Desair
 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
 Esperantolaan 4, Heverlee 3001, Belgium
 www.atmire.com
 

 2016-12-07 20:45 GMT+01:00 Alan Orth :

> Hi, George.
>
> You should absolutely be using a git-based workflow. First, git is fun
> and cool and much better in every way than CVS/SVN, but it's also the
> official version control of the DSpace project itself since about 2014
> or so. This is important for cherry-picking patches, rebasing your
> local changes on top of upstream point releases, etc.
>
> Second, GitHub is great. We forked DSpace's DSpace repository there
> and I cherry-pick commits from their branch from time to time, as well
> as rebase on their point releases as I mentioned above. Even though
> I'm basically the only technical one doing DSpace on our team, I make
> *extensive* use of GitHub other features like issues, pull requests,
> and wikis. For example, when a user reports a bug or feature, I create
> an issue to track it, then when I get time to address it I make a pull
> request to my institution's repository from my personal repository.
>
> Here's our

Re: [dspace-tech] Git Rebase Issue

2016-12-08 Thread helix84 
The last command should have been just:

git push terrywbrady ds3282 --force


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Git Rebase Issue

2016-12-08 Thread helix84 
The problem is that the same changeset is there twice (commit with the
same content). What the diff doesn't exactly show you why that is. If
you want to see that, take a look at the DAG using a tool like gitk or
gitg or what have you. You'll see that each of them is on a different
branch and when you merged them, one of them became a no-op.

There are two possible approches how to fix it (result is the same),
cherry-pick or rebase:

git checkout master
git pull upstream master

git checkout -b ds3282-new

git cherry-pick a7ffd60
git push terrywbrady ds3282-new:ds3282 --force

or

git checkout --track terrywbrady/ds3282
git rebase -i master

pick a7ffd60 Fix js error for filters with dashes
drop ecf6f42 Fix js error for filters with dashes

git push terrywbrady ds3282-new:ds3282 --force


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Embargoed bitstreams can be accessed

2016-12-08 Thread Tom Desair 
Hi Gary,

This bug has been reported here https://jira.duraspace.org/browse/DS-3097
and is fixed in more recent DSpace versions.

It is important to realise that resource policies have to be defined on
item level and on bitstream level. When downloading a bitstream, only the
resource policies on the bitstream level are checked. Configuring an
embargo on item level does not automatically apply it to all bitstreams. In
this example (XMLUI) the item is embargoed but the bitstream is not:
[image: Inline afbeelding 1]

Best regards,
Tom


[image: logo] Tom Desair
250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
Esperantolaan 4, Heverlee 3001, Belgium
www.atmire.com


2016-12-08 4:54 GMT+01:00 Gary Browne :

> Hi all,
>
> Using:
>
> DSpace JSPUI v 4.1
> RHEL 6
> Tomcat 7
> Apache 2.2
>
> Bitstreams of items that are embargoed can be accessed by obtaining the
> link (either from source HTML or right-clicking the bitstream link). Is
> there something wrong with our DSpace setup or is does embargo not limit
> bitstream-level access?
>
> I tried removing all resource policies from a sample embargoed item but I
> was still able to access it.
>
> Thanks,
> Gary
>
> --
> 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 dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> 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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.