Re: [dspace-tech] Request Document Copy Large Files – DSpace 6 XMLUI

[eneshukic via DSpace Technical Support]

Hi Tim and Adan,

Thanks for your input.  We have considered using an Embargo, but it would 
not meet our requirements.

We would probably need to handle the mail server error message  and add 
another button that will notify the requester that the file is too large to 
be sent by mail (and offer them other methods to get the document).

We would probably need to implement something similar to Adan.

Regards,
Enes

On Monday, September 24, 2018 at 5:21:54 PM UTC+2, Adan Roman Ruiz wrote:
>
> We solved using other method. Although it needs changes in the source 
> code. 
> First we alter the request-copy to send links with a generated 
> token  (very long), instead of the file. We store into the database the 
> token, related file, date and uses.
> Then we added a point of access to dspace similar to /bitstream called 
> /itemRequestFileDownload. This access point checks that the token exists, 
> and returns the related file ignoring permissions.
> In addition you can record the number of uses, or use the time passed from 
> its generated, to make expire the link.
>
> Best luck
> Adán Roman
>
> El lun., 24 sept. 2018 a las 16:35, Tim Donohue ( >) escribió:
>
>> Hi Enes,
>>
>> If you are willing to create a DSpace *group* to provide access to the 
>> document, then you could manage this access similar to a DSpace Embargo:
>>
>> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-DSpaceEmbargoFunctionality
>>
>> In DSpace, an Embargo is simply provides temporary access and/or 
>> restrictions on an entire Item or a specific file (Bitstream).  However, 
>> those temporary access rights are only available to be set at the Group 
>> level (not at an individual EPerson).  But, if you are willing to create a 
>> Group for this scenario, then you could Edit the Item, and add a new 
>> "authorization policy (also known as a "Resource Policy") (on either the 
>> entire Item, or a single Bitstream). You'd want to define a new policy that 
>> provides READ access to a specific Group, and add an "End Date" of one 
>> day/week/month from now.  Once the "End Date" passes, the policy will 
>> expire, and the access rights provided by the policy will no longer be 
>> valid.
>>
>> I hope that gives you an idea of another way to provide temporary access 
>> rights.  Let us know on this list if you have other questions.
>>
>> Tim
>>
>>
>>
>> On Mon, Sep 24, 2018 at 6:17 AM eneshukic via DSpace Technical Support <
>> dspac...@googlegroups.com > wrote:
>>
>>> If a registered user is requesting a copy of large bitstream document, 
>>> mail server will return an error message.
>>>
>>>
>>> What are the other way of distributing large documents? We can export 
>>> the item (zip file) and place it into shared folder, but that is not the 
>>> most efficient and secure way to do it. Can we grant a temporary user 
>>> access to the bitstream?
>>>
>>>
>>> Regards,
>>>
>>> Enes 
>>>
>>> -- 
>>> All messages to this mailing list should adhere to the DuraSpace Code of 
>>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>>> --- 
>>> 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.
>>>
>> -- 
>> Tim Donohue
>> Technical Lead for DSpace & DSpaceDirect
>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>
>> -- 
>> All messages to this mailing list should adhere to the DuraSpace Code of 
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> --- 
>> 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.
>>
>
>
> -- 
> Adán Román Ruiz
> adan@gmail.com 
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] Request Document Copy Large Files – DSpace 6 XMLUI

[eneshukic via DSpace Technical Support]

 

If a registered user is requesting a copy of large bitstream document, mail 
server will return an error message.


What are the other way of distributing large documents? We can export the 
item (zip file) and place it into shared folder, but that is not the most 
efficient and secure way to do it. Can we grant a temporary user access to 
the bitstream?


Regards,

Enes 

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Mirage2 & xmlui "file not found" error

[eneshukic via DSpace Technical Support]

Hi Juliana,

The installation process is trying to get Bower version that is defined in 
the package.json (probably 1.7.4).  Try this:

1. Make sure that you have the latest Bower version 1.8.4 installed on your 
machine (npm install -g bower). Also, install other Mirage 2 components  
https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2 .
2. Change Bower version in package.json to 1.8.4 
(dspace-xmlui-mirage2\src\main\webapp).
3. Build again.

mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false

Regards,
Enes

On Wednesday, August 15, 2018 at 5:47:57 AM UTC+2, Juliana Vasconcelos 
Braga wrote:
>
> Hello everyone!
>
> I have the same issue! I tried a lot of things but nothing worked
>
> I'm using Dspace 6.2, instaled and running on a windows 7 system. 
> Maven returned a error with a message about some Bower packages. Then I 
> tried install the packages manually, but the message error from Bower 
> indicates that the versions of packages are no  longer available (Message: 
> bower ENOTFOUND Package not found), so I've installed the new versions of 
> packages, but Maven continues to return the same errors. 
>
> I'm attaching a printscreen from error.
>
> Best regards for you all,
> Juliana.
> Em quinta-feira, 12 de julho de 2018 09:19:39 UTC-3, Sorin Solomon 
> escreveu:
>>
>> Hi, everyone.
>>
>> I installed DSpace 6 on Ubuntu 18.04, following the instructions in the 
>> wiki .
>> All finished successfully, but when I go to [IP Address]:8080/xmlui I get 
>> the error message shown in the attached screenshot.
>> I searched the Support Forum and I found this issue in the past. 
>> I checked, it's not an issue of permissions 
>> .
>>  
>> I also tried to change permissions on the /root folder (like in this 
>> article 
>> ), 
>> same result. I even tried to run mvn -U clean package -Dmirage2.on=true 
>> (like 
>> shown here 
>> ), 
>> but the result is the same. 
>>
>> I'm pretty out of ideas here. Help?
>>
>> Thank you in advance for your assistance.
>>
>> Sorin Solomon
>>
>>
>>
>>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Mirage2 & xmlui "file not found" error

[eneshukic via DSpace Technical Support]

Hi Sorin,

There are two options for the installation (*dspace-n.x-release.* and 
*dspace-n.x-src-release.zzz*).  I am using the source zip.  This is the 
full path to package.json is located at the 
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui-mirage2/src/main/webapp/package.json
 
. The other option is to  copy it to your mirage2 customization directory 
(dspace\modules\xmlui-mirage2\src\main\webapp).

Regards,
Enes



On Tuesday, August 14, 2018 at 9:14:17 AM UTC+2, Sorin Solomon wrote:
>
> No such path for me.
> I installed following these instructions: 
> https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-WindowsInstallation
>  
> .
> I did not want to deal with Mirage2 prerequisites, so installed it using mvn 
> package -Dmirage2.on=true . Everything completed successfully. But it 
> doesn't work.
>
> Any ideas why I don't have that folders' tree?
>
> Sorin
>
> On Monday, August 13, 2018 at 8:00:00 PM UTC+3, enes...@yahoo.com wrote:
>>
>> It is located in the [dspace-src]\dspace-xmlui-mirage2\src\main\webapp 
>> directory. 
>>
>> Enes
>> On Monday, August 13, 2018 at 3:55:14 PM UTC+2, Sorin Solomon wrote:
>>>
>>> Thanks for the prompt response, Enes.
>>> Can you give me the full path to the package.json? Can't find it with 
>>> locate. I wonder if it's missing or I'm not using locate properly ...
>>>
>>> TIA.
>>>
>>> Sorin
>>>
>>> On Monday, August 13, 2018 at 4:29:13 PM UTC+3, enes...@yahoo.com wrote:

 Hi Sorin,


 Did you change Bower version to 1.8.4 in package.json file 
 (dspace-xmlui-mirage2\src\main\webapp)? 


 You can also install Mirage 2 components on your server 
 https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2 .


 Then, you can run: mvn -U clean package -Dmirage2.on=true 
 -Dmirage2.deps.included=false .


 Regards,

 Enes


 On Monday, August 13, 2018 at 1:53:32 PM UTC+2, Sorin Solomon wrote:
>
> Sorry it took me so long. Busy days.
>
> Installed Bower, as you suggested. Then compiled DSpace from scratch.
>
> No luck. Still same error message when trying to access IP:8080/xmlui:
>
> ' Syntax error: File to import not found or unreadable: 
> ../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap. '
>
> The error I get is on line 16 of styles/main.scss. That line states:
> ' @import 
> "../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap"; '
>
> I ran ' updatedb ' and then ' locate bootstrap-sass-official ' and 
> there are no results. How come ?
>
> Any ideas?
>
> Sorin
>
> On Tuesday, August 7, 2018 at 4:11:58 PM UTC+3, enes...@yahoo.com 
> wrote:
>>
>> Hi Sorin,
>>
>>
>> I was able to resolve this issue:
>>
>>
>> 1. Make sure that you have the latest Bower version 1.8.4 installed 
>> on your machine (npm install -g bower).
>>
>> 2. Change Bower version in package.json 
>> (dspace-xmlui-mirage2\src\main\webapp).
>>
>> 3. Build again.
>>
>>
>> mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false
>>
>>
>> Regards,
>>
>> Enes
>>
>>
>> On Thursday, July 12, 2018 at 2:19:39 PM UTC+2, Sorin Solomon wrote:
>>>
>>> Hi, everyone.
>>>
>>> I installed DSpace 6 on Ubuntu 18.04, following the instructions in 
>>> the wiki 
>>> .
>>> All finished successfully, but when I go to [IP Address]:8080/xmlui 
>>> I get the error message shown in the attached screenshot.
>>> I searched the Support Forum and I found this issue in the past. 
>>> I checked, it's not an issue of permissions 
>>> .
>>>  
>>> I also tried to change permissions on the /root folder (like in 
>>> this article 
>>> ),
>>>  
>>> same result. I even tried to run mvn -U clean package -Dmirage2.on=
>>> true (like shown here 
>>> ),
>>>  
>>> but the result is the same. 
>>>
>>> I'm pretty out of ideas here. Help?
>>>
>>> Thank you in advance for your assistance.
>>>
>>> Sorin Solomon
>>>
>>>
>>>
>>>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] Re: Mirage2 & xmlui "file not found" error

[eneshukic via DSpace Technical Support]

It is located in the [dspace-src]\dspace-xmlui-mirage2\src\main\webapp 
directory. 

Enes
On Monday, August 13, 2018 at 3:55:14 PM UTC+2, Sorin Solomon wrote:
>
> Thanks for the prompt response, Enes.
> Can you give me the full path to the package.json? Can't find it with 
> locate. I wonder if it's missing or I'm not using locate properly ...
>
> TIA.
>
> Sorin
>
> On Monday, August 13, 2018 at 4:29:13 PM UTC+3, enes...@yahoo.com wrote:
>>
>> Hi Sorin,
>>
>>
>> Did you change Bower version to 1.8.4 in package.json file 
>> (dspace-xmlui-mirage2\src\main\webapp)? 
>>
>>
>> You can also install Mirage 2 components on your server 
>> https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2 .
>>
>>
>> Then, you can run: mvn -U clean package -Dmirage2.on=true 
>> -Dmirage2.deps.included=false .
>>
>>
>> Regards,
>>
>> Enes
>>
>>
>> On Monday, August 13, 2018 at 1:53:32 PM UTC+2, Sorin Solomon wrote:
>>>
>>> Sorry it took me so long. Busy days.
>>>
>>> Installed Bower, as you suggested. Then compiled DSpace from scratch.
>>>
>>> No luck. Still same error message when trying to access IP:8080/xmlui:
>>>
>>> ' Syntax error: File to import not found or unreadable: 
>>> ../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap. '
>>>
>>> The error I get is on line 16 of styles/main.scss. That line states:
>>> ' @import 
>>> "../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap"; '
>>>
>>> I ran ' updatedb ' and then ' locate bootstrap-sass-official ' and 
>>> there are no results. How come ?
>>>
>>> Any ideas?
>>>
>>> Sorin
>>>
>>> On Tuesday, August 7, 2018 at 4:11:58 PM UTC+3, enes...@yahoo.com wrote:

 Hi Sorin,


 I was able to resolve this issue:


 1. Make sure that you have the latest Bower version 1.8.4 installed on 
 your machine (npm install -g bower).

 2. Change Bower version in package.json 
 (dspace-xmlui-mirage2\src\main\webapp).

 3. Build again.


 mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false


 Regards,

 Enes


 On Thursday, July 12, 2018 at 2:19:39 PM UTC+2, Sorin Solomon wrote:
>
> Hi, everyone.
>
> I installed DSpace 6 on Ubuntu 18.04, following the instructions in 
> the wiki 
> .
> All finished successfully, but when I go to [IP Address]:8080/xmlui I 
> get the error message shown in the attached screenshot.
> I searched the Support Forum and I found this issue in the past. 
> I checked, it's not an issue of permissions 
> .
>  
> I also tried to change permissions on the /root folder (like in this 
> article 
> ), 
> same result. I even tried to run mvn -U clean package -Dmirage2.on=
> true (like shown here 
> ), 
> but the result is the same. 
>
> I'm pretty out of ideas here. Help?
>
> Thank you in advance for your assistance.
>
> Sorin Solomon
>
>
>
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Mirage2 & xmlui "file not found" error

[eneshukic via DSpace Technical Support]

 

Hi Sorin,


Did you change Bower version to 1.8.4 in package.json file 
(dspace-xmlui-mirage2\src\main\webapp)? 


You can also install Mirage 2 components on your server 
https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2 .


Then, you can run: mvn -U clean package -Dmirage2.on=true 
-Dmirage2.deps.included=false .


Regards,

Enes


On Monday, August 13, 2018 at 1:53:32 PM UTC+2, Sorin Solomon wrote:
>
> Sorry it took me so long. Busy days.
>
> Installed Bower, as you suggested. Then compiled DSpace from scratch.
>
> No luck. Still same error message when trying to access IP:8080/xmlui:
>
> ' Syntax error: File to import not found or unreadable: 
> ../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap. '
>
> The error I get is on line 16 of styles/main.scss. That line states:
> ' @import 
> "../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap"; '
>
> I ran ' updatedb ' and then ' locate bootstrap-sass-official ' and there 
> are no results. How come ?
>
> Any ideas?
>
> Sorin
>
> On Tuesday, August 7, 2018 at 4:11:58 PM UTC+3, enes...@yahoo.com wrote:
>>
>> Hi Sorin,
>>
>>
>> I was able to resolve this issue:
>>
>>
>> 1. Make sure that you have the latest Bower version 1.8.4 installed on 
>> your machine (npm install -g bower).
>>
>> 2. Change Bower version in package.json 
>> (dspace-xmlui-mirage2\src\main\webapp).
>>
>> 3. Build again.
>>
>>
>> mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false
>>
>>
>> Regards,
>>
>> Enes
>>
>>
>> On Thursday, July 12, 2018 at 2:19:39 PM UTC+2, Sorin Solomon wrote:
>>>
>>> Hi, everyone.
>>>
>>> I installed DSpace 6 on Ubuntu 18.04, following the instructions in the 
>>> wiki .
>>> All finished successfully, but when I go to [IP Address]:8080/xmlui I 
>>> get the error message shown in the attached screenshot.
>>> I searched the Support Forum and I found this issue in the past. 
>>> I checked, it's not an issue of permissions 
>>> .
>>>  
>>> I also tried to change permissions on the /root folder (like in this 
>>> article 
>>> ), 
>>> same result. I even tried to run mvn -U clean package -Dmirage2.on=true 
>>> (like shown here 
>>> ), 
>>> but the result is the same. 
>>>
>>> I'm pretty out of ideas here. Help?
>>>
>>> Thank you in advance for your assistance.
>>>
>>> Sorin Solomon
>>>
>>>
>>>
>>>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Mirage2 & xmlui "file not found" error

[eneshukic via DSpace Technical Support]

 

Hi Sorin,


I was able to resolve this issue:


1. Make sure that you have the latest Bower version 1.8.4 installed on your 
machine (npm install -g bower).

2. Change Bower version in package.json 
(dspace-xmlui-mirage2\src\main\webapp).

3. Build again.


mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false


Regards,

Enes


On Thursday, July 12, 2018 at 2:19:39 PM UTC+2, Sorin Solomon wrote:
>
> Hi, everyone.
>
> I installed DSpace 6 on Ubuntu 18.04, following the instructions in the 
> wiki .
> All finished successfully, but when I go to [IP Address]:8080/xmlui I get 
> the error message shown in the attached screenshot.
> I searched the Support Forum and I found this issue in the past. 
> I checked, it's not an issue of permissions 
> .
>  
> I also tried to change permissions on the /root folder (like in this 
> article 
> ), 
> same result. I even tried to run mvn -U clean package -Dmirage2.on=true (like 
> shown here 
> ), 
> but the result is the same. 
>
> I'm pretty out of ideas here. Help?
>
> Thank you in advance for your assistance.
>
> Sorin Solomon
>
>
>
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Mirage2 & xmlui "file not found" error

[eneshukic via DSpace Technical Support]

Hi Sorin and Tim,

I have tried to rebuild one of my instances yesterday and I am getting the 
same error.

mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false

My output where the error occurs looks like this:

[INFO] -- (Mirage2) org.codehaus.mojo:exec-maven-plugin:1.4.0:exec
npm WARN deprecated bower@1.7.9: ...psst! Your project can stop working at 
any moment because its dependencies can change. Prevent this by migrating 
to Yarn: https://bower.io/blog/2017/how-to-migrate-away-from-bower/

> Mirage2@0.1.2 postinstall 
/home/dspace/dspace-src-fgu66/dspace/modules/xmlui-mirage2/target/themes/Mirage2
> bower install

bower jquery-ui#1.10.3 EINVRES Request to 
https://bower.herokuapp.com/packages/jquery-ui failed with 502
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! Mirage2@0.1.2 postinstall: `bower install`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the Mirage2@0.1.2 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely 
additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/dspace/.npm/_logs/2018-08-07T09_02_12_274Z-debug.log
[INFO] 

[INFO] Reactor Summary:
[INFO] 
[INFO] DSpace Parent Project .. SUCCESS [  
0.987 s]
[INFO] DSpace Services Framework :: API and Implementation  SUCCESS [  
5.304 s]
[INFO] DSpace Kernel :: API and Implementation  SUCCESS [ 
23.414 s]
[INFO] DSpace Addon Modules ... SUCCESS [  
0.005 s]
[INFO] DSpace Kernel :: Additions and Local Customizations  SUCCESS [  
7.259 s]
[INFO] DSpace XML-UI (Manakin)  SUCCESS [ 
12.140 s]
[INFO] DSpace XML-UI Mirage2 Theme  SUCCESS [  
0.416 s]
[INFO] DSpace XML-UI Mirage2 Theme :: Local Customisations  FAILURE [ 
31.754 s]
[INFO] DSpace XML-UI (Manakin) :: Local Customizations  SKIPPED
[INFO] DSpace JSP-UI .. SKIPPED
[INFO] DSpace JSP-UI :: Local Customizations .. SKIPPED
[INFO] DSpace RDF . SKIPPED
[INFO] DSpace RDF :: Local Customizations . SKIPPED
[INFO] DSpace REST :: API and Implementation .. SKIPPED
[INFO] DSpace REST :: Local Customizations  SKIPPED
[INFO] DSpace SWORD ... SKIPPED
[INFO] DSpace SWORD :: Local Customizations ... SKIPPED
[INFO] DSpace SWORD v2  SKIPPED
[INFO] DSpace SWORD v2 :: Local Customizations  SKIPPED
[INFO] Apache Solr Webapp . SKIPPED
[INFO] DSpace SOLR :: Local Customizations  SKIPPED
[INFO] DSpace OAI-PMH . SKIPPED
[INFO] DSpace OAI-PMH :: Local Customizations . SKIPPED
[INFO] DSpace Assembly and Configuration .. SKIPPED
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 01:22 min
[INFO] Finished at: 2018-08-07T11:02:12+02:00
[INFO] Final Memory: 77M/523M
[INFO] 

[ERROR] Failed to execute goal 
com.soebes.maven.plugins:iterator-maven-plugin:0.3:iterator (default) on 
project xmlui-mirage2: Command execution failed.: Process exited with an 
error: 1 (Exit value: 1) -> [Help 1]

My debug log: 

6601 silly lifecycle Mirage2@0.1.2~postinstall: Args: [ '-c', 'bower 
install' ]
6602 silly lifecycle Mirage2@0.1.2~postinstall: Returned: code: 1  signal: 
null
6603 info lifecycle Mirage2@0.1.2~postinstall: Failed to exec postinstall 
script
6604 verbose stack Error: Mirage2@0.1.2 postinstall: `bower install`
6604 verbose stack Exit status 1
6604 verbose stack at EventEmitter. 
(/home/dspace/.nvm/versions/node/v8.7.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:280:16)
6604 verbose stack at emitTwo (events.js:125:13)
6604 verbose stack at EventEmitter.emit (events.js:213:7)
6604 verbose stack at ChildProcess. 
(/home/dspace/.nvm/versions/node/v8.7.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
6604 verbose stack at emitTwo (events.js:125:13)
6604 verbose stack at ChildProcess.emit (events.js:213:7)
6604 verbose stack at maybeClose (internal/child_process.js:927:16)
6604 verbose stack at Process.ChildProcess._handle.onexit 
(internal/child_process.js:211:5)
6605 verbose pkgid Mirage2@0.1.2
6606 verbose cwd 
/home/dspace/dspace-src-fgu66/dspace/modules/xmlui-mirage2/target/themes/Mirage2
6607 verbose Linux 3.10.0-693.el7.x86_64
6608 verbose argv "/home/dspace/.nvm/versions/node/v8.7.0/bin/node" 
"/home/dspace/.nvm/versions/node/v8.7.0/bin/npm" "install"
6609 verbose node v8.7.0
6610 

Re: [dspace-tech] Curation tasks on DSpace 6 stoped working

[eneshukic via DSpace Technical Support]

 

Hi Tim,

I was able to solve this issue. It was tied to input forms. Our instance is 
multilingual (4 languages) . It looks like that someone was changing 
translation versions of the input form, while the main version was 
unchanged or there was mismatch. The main input form form was syntactically 
correct. At the same time, around 100GB of data was imported into system. 
When I have replaced the main input form with earlier version, everything 
started to function again.


Thanks again for your help. 


Regards,

Enes


On Wednesday, March 28, 2018 at 4:22:53 PM UTC+2, Tim Donohue wrote:
>
> Hi Enes,
>
> Sorry, I've run out of ideas here.  As you aren't able to reproduce this 
> on another server, and I cannot reproduce this on my end (or on 
> demo.dspace.org), it seems to me it's likely to be one of the following 
> (but I don't know which one):
>
> 1. A configuration problem in either curate.cfg or dspace.cfg
> 2. A code customization issue -- where some Java code was customized in 
> the DSpace API, and it's breaking how the Curation code normally functions
> 3. Possibly (though less likely) a DSpace upgrade issue, where some old 
> code is still "in place" (like an old JAR file or something) that is 
> conflicting with the current code.
>
> That's my best guess here. If we could find a way to reproduce this issue 
> elsewhere, we might be able to narrow down the issue better.  But, without 
> reproducibility, I'm mostly just guessing at things that could be different 
> on this server.  
>
> You also might want to brainstorm what changed about this server recently, 
> as it sounds like something must have changed in order for it to stop 
> working suddenly... e.g. if you upgraded recently, maybe the upgrade messed 
> something up.  If you changed a configuration recently, maybe try undoing 
> recent config changes to see if they had an effect.  If you implemented 
> some custom code recently, maybe try undoing that to see if that could be 
> the cause.
>
> Sorry I cannot be of more help.  If you figure out more about what could 
> be going on, please do let us know on this list (especially if you start to 
> narrow down the cause). It really could help others to debug issues that 
> they see that might be similar in the future.
>
> Good luck,
>
> Tim
>
> On Tue, Mar 27, 2018 at 6:25 PM eneshukic via DSpace Technical Support <
> dspac...@googlegroups.com > wrote:
>
>> Hi Tim,
>>
>> I have tried to copy the original curate.cfg, but it is the same 
>> outcome.  I do not thing that it is the problem with curate.cfg.  The 
>> strange thing is that curation tasks have worked on this server for several 
>> months and tnen stopped working.
>>
>> Regards,
>> Enes
>>
>>
>> On Monday, March 26, 2018 at 7:57:56 PM UTC+2, Tim Donohue wrote:
>>
>>> Hi Enes,
>>>
>>> Huh, that is weird.  That configuration / output looks perfectly 
>>> reasonable to me, and I see it includes an entry named "requiredmetadata" 
>>> which is the exact task that threw the "Task: requiredmetadata not 
>>> resolved" error.   So, that's very odd to me... DSpace seems to see you 
>>> have a configuraiton for "requiredmetadata" but cannot find it when it 
>>> tries to run it.
>>>
>>> To be honest, that's a bit baffling to me.
>>>
>>> One thing you could try is to temporarily replace your configurations 
>>> with the *default* configurations from DSpace 6.x.  For example, copy the 
>>> curate.cfg for DSpace 6.x from here: 
>>> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/modules/curate.cfg
>>>   
>>>  And then double check that you have this "include" line in your 
>>> dspace.cfg: 
>>> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/dspace.cfg#L2005
>>>
>>> After you've temporarily changed your configs, try running the 
>>> "requiredmetadata" task again.  If it works, then that implies one of the 
>>> other custom configs in your curate.cfg might be to blame...you can add 
>>> them back in one-by-one to see which one causes the failure.  If it still 
>>> doesn't work, then it's not your curate.cfg file at all.
>>>
>>> - Tim
>>>
>>>
>>> On Fri, Mar 23, 2018 at 7:52 PM eneshukic via DSpace Technical Support <
>>> dspac...@googlegroups.com> wrote:
>>>
>>>> Hi Tim,
>>>>
>>>> I executed:
>>>> dspace/bin/dspace dsprop -p plugin.named.org.dspace.curate.CurationTask 
>>>>

Re: [dspace-tech] Curation tasks on DSpace 6 stoped working

[eneshukic via DSpace Technical Support]

Hi Tim,

I executed:
dspace/bin/dspace dsprop -p plugin.named.org.dspace.curate.CurationTask -r

My output is:
[org.dspace.ctask.general.NoOpCurationTask = noop, 
org.dspace.ctask.general.ProfileFormats = profileformats, 
org.dspace.ctask.general.RequiredMetadata = requiredmetadata, 
org.dspace.ctask.general.ClamScan = vscan, 
org.dspace.ctask.general.MicrosoftTranslator = translate, 
org.dspace.ctask.general.MetadataValueLinkChecker = checklinks, 
org.dspace.ctask.general.ValidateMetadata = validatemetadata, 
org.dspace.ctask.general.ExtractMBRfromTFW = extractmbr, 
org.dspace.ctask.general.InheritCollectionPermissions = 
collectionpermission, org.dspace.ctask.general.DeleteReplicationItems = 
deletereplicationitems]

It looks correct.  Do you have any ideas what else could cause not resolved 
issue?

Thanks,
Enes


On Thursday, March 22, 2018 at 6:27:18 PM UTC+1, Tim Donohue wrote:
>
> Hi Enes,
>
> To me, that error "Task: requiredmetadata not resolved", still sounds 
> suspiciously like a configuration problem.  So, I'm wondering if your 
> primary configuration in curate.cfg is being accidentally overridden 
> elsewhere (e.g. in local.cfg), or perhaps if the curate.cfg files isn't 
> being loaded into your dspace.cfg properly (e.g. via an "include" line like 
> this: 
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/dspace.cfg#L2005
> )
>
> One thing you could try... DSpace has a commandline tool that is able to 
> check what configurations it "sees".   Try running:
>
> [dspace]/bin/dspace dsprop -p plugin.named.org.dspace.curate.CurationTask 
> -r
>
> This should output the "raw" (-r) value of the 
> "plugin.named.org.dspace.curate.CurationTask" 
> configuration that DSpace is loading/seeing.  In a normal, default 6.x 
> DSpace site, this command should return an array of values like this:
>
> [org.dspace.ctask.general.NoOpCurationTask = noop, 
> org.dspace.ctask.general.ProfileFormats = profileformats, 
> org.dspace.ctask.general.RequiredMetadata =
> requiredmetadata, org.dspace.ctask.general.ClamScan = vscan, 
> org.dspace.ctask.general.MicrosoftTranslator = translate, 
> org.dspace.ctask.general.MetadataValueLinkChecker = checklinks]
>
> This array of values is defined in the curate.cfg file.  If your site does 
> *not* return this array of values, then something is definitely wrong in 
> your configuration.
>
> - Tim
>
> On Thu, Mar 22, 2018 at 5:54 AM eneshukic via DSpace Technical Support <
> dspac...@googlegroups.com > wrote:
>
>> Hi Tim,
>>
>> This happens on every curation task that I run on this machine.  For 
>> example:
>>
>> dspace/bin/dspace curate -t requiredmetadata -i 123456789/3770 -r - -v
>> Adding task: requiredmetadata
>> Task: requiredmetadata not resolved
>> Starting curation
>> Curating id: 123456789/3770
>> Ending curation. Elapsed time: 576
>>
>> The same command works on the other two machines and my test machine. It 
>> was working too on this machine for couple of months and it stopped. 
>> Configurations are the same on all instances. It looks like that this 
>> problem occurs while task is getting resolved in Curator.java.  
>>
>> I have even tried to rebuild, but I get the same issue.  Is there 
>> anything else that I need to check (maybe at the OS level)?
>>
>> Regards,
>> Enes
>>
>>
>> On Wednesday, March 21, 2018 at 8:24:01 PM UTC+1, Tim Donohue wrote:
>>
>>> Hi Enes,
>>>
>>> I just did a basic test of Curation Tasks on our http://demo.dspace.org 
>>> server.  On that server, I ran the following on the commandline:
>>>
>>> [dspace]/bin/dspace curate -t checklinks -i 10673/5 -r - -v
>>>
>>> And, the "checklinks" curation task ran successfully on this item: 
>>> http://demo.dspace.org/xmlui/handle/10673/5 without any issues.
>>>
>>> So, I'm wondering if maybe it's a configuration error on your end, or if 
>>> only specific task(s) are failing.  But, we'd probably need you to send 
>>> more information to the mailing list in order to help diagnose the issue.  
>>> In any case, I'd recommend double checking that your curation task 
>>> configuration, perhaps comparing it the the out-of-the-box DSpace 6.x 
>>> version:
>>>
>>>
>>> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/modules/curate.cfg
>>>
>>> (And where the configuration exists shouldn't matter too much, but any 
>>> configurations in your local.cfg *will override* the settings in your 
>>> curate.cfg)
>>>
>>> - T

Re: [dspace-tech] Curation tasks on DSpace 6 stoped working

[eneshukic via DSpace Technical Support]

Hi Tim,

This happens on every curation task that I run on this machine.  For 
example:

dspace/bin/dspace curate -t requiredmetadata -i 123456789/3770 -r - -v
Adding task: requiredmetadata
Task: requiredmetadata not resolved
Starting curation
Curating id: 123456789/3770
Ending curation. Elapsed time: 576

The same command works on the other two machines and my test machine. It 
was working too on this machine for couple of months and it stopped. 
Configurations are the same on all instances. It looks like that this 
problem occurs while task is getting resolved in Curator.java.  

I have even tried to rebuild, but I get the same issue.  Is there anything 
else that I need to check (maybe at the OS level)?

Regards,
Enes

On Wednesday, March 21, 2018 at 8:24:01 PM UTC+1, Tim Donohue wrote:
>
> Hi Enes,
>
> I just did a basic test of Curation Tasks on our http://demo.dspace.org 
> server.  On that server, I ran the following on the commandline:
>
> [dspace]/bin/dspace curate -t checklinks -i 10673/5 -r - -v
>
> And, the "checklinks" curation task ran successfully on this item: 
> http://demo.dspace.org/xmlui/handle/10673/5 without any issues.
>
> So, I'm wondering if maybe it's a configuration error on your end, or if 
> only specific task(s) are failing.  But, we'd probably need you to send 
> more information to the mailing list in order to help diagnose the issue.  
> In any case, I'd recommend double checking that your curation task 
> configuration, perhaps comparing it the the out-of-the-box DSpace 6.x 
> version:
>
>
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/modules/curate.cfg
>
> (And where the configuration exists shouldn't matter too much, but any 
> configurations in your local.cfg *will override* the settings in your 
> curate.cfg)
>
> - Tim
>
> On Wed, Mar 21, 2018 at 7:32 AM eneshukic via DSpace Technical Support <
> dspac...@googlegroups.com > wrote:
>
>> We have three DSpace 6 instances on CentOS 7.  On one instance, curation 
>> tasks are not working from either CLI, XMLUI or our custom forms. The 
>> configuration is the same on all three instances.  If we run dspace curate 
>> -t taskname -i 123456789/3770 -r - -v , we get Task: taskname not 
>> resolved.  This includes curation tasks that come out of box. 
>>
>> We have also tried to move setting from the curate.cfg to local.cfg, but 
>> the same issue is occurring.
>>
>> Did anyone experience similar issue?
>>
>> Regards,
>> Enes
>>
>> -- 
>> 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.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
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] Curation tasks on DSpace 6 stoped working

[eneshukic via DSpace Technical Support]

We have three DSpace 6 instances on CentOS 7.  On one instance, curation 
tasks are not working from either CLI, XMLUI or our custom forms. The 
configuration is the same on all three instances.  If we run dspace curate 
-t taskname -i 123456789/3770 -r - -v , we get Task: taskname not 
resolved.  This includes curation tasks that come out of box. 

We have also tried to move setting from the curate.cfg to local.cfg, but 
the same issue is occurring.

Did anyone experience similar issue?

Regards,
Enes

-- 
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: Submission Problem in DSpace 6.2

[eneshukic via DSpace Technical Support]

Hi George,

I have seen this error on the Control panel harvesting tab, but submittion 
is working fine.  This same error is occuring on demo.dspace.org.

Enes

On Monday, November 27, 2017 at 5:46:02 PM UTC+1, George Kozak wrote:
>
> Hi,
> We are moving to upgrade our production server (which is running DSpace 
> 5.5) to Dspace 6.2.  In our testing, we have found a problem with 
> submissions.  When someone submits an item the following error appears: 
> "could not initialize proxy - no Session".
> Has anyone ecountered this before?
>
> The underlining stack trace shows:
> Java stacktrace: org.hibernate.LazyInitializationException: could not 
> initialize proxy - no Session at 
> org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:165)
>  
> at 
> org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:286)
>  
> at 
> org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:185)
>  
> at 
> org.dspace.content.Bitstream_$$_jvstdfd_c.getID(Bitstream_$$_jvstdfd_c.java) 
> at org.dspace.app.xmlui.utils.DSpaceValidity.add(DSpaceValidity.java:325) 
> at org.dspace.app.xmlui.utils.DSpaceValidity.add(DSpaceValidity.java:280) 
> at 
> org.dspace.app.xmlui.aspect.versioning.Navigation.getValidity(Navigation.java:129)
>  
> at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  
> at java.lang.reflect.Method.invoke(Method.java:606) at 
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>  
> at com.sun.proxy.$Proxy226.getValidity(Unknown Source) at 
> org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.getValidityForInternalPipeline(AbstractCachingProcessingPipeline.java:987)
>  
> at ...
>
> -- 
> ***
> George Kozak
> Digital Library Specialist
> Cornell University Library - IT
> 218 Olin Library
> Cornell University
> Ithaca, NY 14853
> 607-255-8924
> gs...@cornell.edu  
>

-- 
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: Submission Problem in DSpace 6.2

[eneshukic via DSpace Technical Support]

Hi George,

I did not see your complete error stack, but you should look for the dspace 
objects.  The error should exactly point out where the problem is.  When 
you find it, change FetchType.Lazy to FetchType.Eager.

Regards,
Enes

On Tuesday, November 28, 2017 at 5:45:02 PM UTC+1, George Kozak wrote:
>
> Enes:
>
> I am unfamiliar with hibernate.  I checked the config 
> file  hibernate.cfg.xml, but did not see anything about changing class from 
> "lazy" to "eager".  Is there somewhere else where this change should be 
> made?
> Thanks,
> George Kozak
> Cornell University
>
> On Tue, Nov 28, 2017 at 6:24 AM, eneshukic via DSpace Technical Support <
> dspac...@googlegroups.com > wrote:
>
>> Hi George,
>>
>> This is Hibernate error.Try changing initaization in your class from 
>> lazy to eager.
>>
>> Regards,
>> Enes
>>
>> On Monday, November 27, 2017 at 5:46:02 PM UTC+1, George Kozak wrote:
>>>
>>> Hi,
>>> We are moving to upgrade our production server (which is running DSpace 
>>> 5.5) to Dspace 6.2.  In our testing, we have found a problem with 
>>> submissions.  When someone submits an item the following error appears: 
>>> "could not initialize proxy - no Session".
>>> Has anyone ecountered this before?
>>>
>>> The underlining stack trace shows:
>>> Java stacktrace: org.hibernate.LazyInitializationException: could not 
>>> initialize proxy - no Session at 
>>> org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:165)
>>>  
>>> at 
>>> org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:286)
>>>  
>>> at 
>>> org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:185)
>>>  
>>> at 
>>> org.dspace.content.Bitstream_$$_jvstdfd_c.getID(Bitstream_$$_jvstdfd_c.java)
>>>  
>>> at org.dspace.app.xmlui.utils.DSpaceValidity.add(DSpaceValidity.java:325) 
>>> at org.dspace.app.xmlui.utils.DSpaceValidity.add(DSpaceValidity.java:280) 
>>> at 
>>> org.dspace.app.xmlui.aspect.versioning.Navigation.getValidity(Navigation.java:129)
>>>  
>>> at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) at 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>  
>>> at java.lang.reflect.Method.invoke(Method.java:606) at 
>>> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>>>  
>>> at com.sun.proxy.$Proxy226.getValidity(Unknown Source) at 
>>> org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.getValidityForInternalPipeline(AbstractCachingProcessingPipeline.java:987)
>>>  
>>> at ...
>>>
>>> -- 
>>> ***
>>> George Kozak
>>> Digital Library Specialist
>>> Cornell University Library - IT
>>> 218 Olin Library
>>> Cornell University
>>> Ithaca, NY 14853
>>> 607-255-8924
>>> gs...@cornell.edu 
>>>
>> -- 
>> 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.
>>
>
>
>
> -- 
> ***
> George Kozak
> Digital Library Specialist
> Cornell University Library - IT
> 218 Olin Library
> Cornell University
> Ithaca, NY 14853
> 607-255-8924
> gs...@cornell.edu  
>

-- 
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: Submission Problem in DSpace 6.2

[eneshukic via DSpace Technical Support]

Hi George,

This is Hibernate error.Try changing initaization in your class from 
lazy to eager.

Regards,
Enes

On Monday, November 27, 2017 at 5:46:02 PM UTC+1, George Kozak wrote:
>
> Hi,
> We are moving to upgrade our production server (which is running DSpace 
> 5.5) to Dspace 6.2.  In our testing, we have found a problem with 
> submissions.  When someone submits an item the following error appears: 
> "could not initialize proxy - no Session".
> Has anyone ecountered this before?
>
> The underlining stack trace shows:
> Java stacktrace: org.hibernate.LazyInitializationException: could not 
> initialize proxy - no Session at 
> org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:165)
>  
> at 
> org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:286)
>  
> at 
> org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:185)
>  
> at 
> org.dspace.content.Bitstream_$$_jvstdfd_c.getID(Bitstream_$$_jvstdfd_c.java) 
> at org.dspace.app.xmlui.utils.DSpaceValidity.add(DSpaceValidity.java:325) 
> at org.dspace.app.xmlui.utils.DSpaceValidity.add(DSpaceValidity.java:280) 
> at 
> org.dspace.app.xmlui.aspect.versioning.Navigation.getValidity(Navigation.java:129)
>  
> at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  
> at java.lang.reflect.Method.invoke(Method.java:606) at 
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>  
> at com.sun.proxy.$Proxy226.getValidity(Unknown Source) at 
> org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.getValidityForInternalPipeline(AbstractCachingProcessingPipeline.java:987)
>  
> at ...
>
> -- 
> ***
> George Kozak
> Digital Library Specialist
> Cornell University Library - IT
> 218 Olin Library
> Cornell University
> Ithaca, NY 14853
> 607-255-8924
> gs...@cornell.edu  
>

-- 
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] Input forms lookup result split into multiple (two) metadata fields based on delimetar (node)

[eneshukic via DSpace Technical Support]

I have created controlled vocabulary with several nodes.  Is there any way 
to store selected values into multiple metadata fields?  For example, If 
user selects Node A ::Node B, value of Node A will go into metadata filed 
someshema.somefield.category and value of nod be will go into fields 
someschema.somefield.subcategory.

Thanks,
Enes

-- 
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] Reports for users, groups and authorizations

[eneshukic via DSpace Technical Support]

Is there any report that lists users and their authorization for each 
community and/or collection?

Thanks,
Enes

-- 
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] Harvesting Items from XMLUI via OAI-ORE or OAI-PMH with metadata parameters

[eneshukic via DSpace Technical Support]

 

Is it possible to harvest items based on metadata value? For example, 
harvest collection items where dc.subject = ‘travel’.


Thanks,

Enes

-- 
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] OAI Harvesting Error: failed to lazily initialize a collection of role

[eneshukic via DSpace Technical Support]

I am getting the following error on all of my dspace instances (it is also 
happening on demo.dspace.org) when Harvester is started from the Control 
Panel:

failed to lazily initialize a collection of role: 
org.dspace.content.DSpaceObject.metadata, could not initialize proxy - no 
Session


Java stacktrace: org.hibernate.LazyInitializationException: failed to 
lazily initialize a collection of role: 
org.dspace.content.DSpaceObject.metadata, could not initialize proxy - no 
Session at 
org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:569)
 
at 
org.hibernate.collection.internal.AbstractPersistentCollection.withTemporarySessionIfNeeded(AbstractPersistentCollection.java:188)
 
at 
org.hibernate.collection.internal.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:548)
 
at 
org.hibernate.collection.internal.AbstractPersistentCollection.read(AbstractPersistentCollection.java:126)
 
at 
org.hibernate.collection.internal.PersistentBag.iterator(PersistentBag.java:266)
 
at 
org.dspace.content.DSpaceObjectServiceImpl.getMetadata(DSpaceObjectServiceImpl.java:129)
 
at 
org.dspace.content.DSpaceObjectServiceImpl.getMetadataFirstValue(DSpaceObjectServiceImpl.java:380)
 
at org.dspace.eperson.EPerson.getFirstName(EPerson.java:253) at 
org.dspace.app.xmlui.utils.DSpaceValidity.add(DSpaceValidity.java:344) at 
org.dspace.app.xmlui.aspect.versioning.Navigation.getValidity(Navigation.java:118)
 
at sun.reflect.GeneratedMethodAccessor148.invoke(Unknown Source) at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
at java.lang.reflect.Method.invoke(Method.java:498) at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
 
at com.sun.proxy.$Proxy212.getValidity(Unknown Source) at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.getValidityForInternalPipeline(AbstractCachingProcessingPipeline.java:987)
 
at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.validatePipeline(AbstractCachingProcessingPipeline.java:601)
 
at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:717)
 
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:466)
 
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.prepareInternal(AbstractProcessingPipeline.java:480)
 
at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source) at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
at java.lang.reflect.Method.invoke(Method.java:498) at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
 
at com.sun.proxy.$Proxy205.prepareInternal(Unknown Source) at 
org.apache.cocoon.components.source.impl.SitemapSource.init(SitemapSource.java:292)
 
at 
org.apache.cocoon.components.source.impl.SitemapSource.(SitemapSource.java:148)
 
at 
org.apache.cocoon.components.source.impl.SitemapSourceFactory.getSource(SitemapSourceFactory.java:62)
 
at 
org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:153)
 
at 
org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:183)
 
at org.apache.cocoon.generation.FileGenerator.setup(FileGenerator.java:99) 
at 
org.dspace.app.xmlui.cocoon.AspectGenerator.setup(AspectGenerator.java:81) 
at sun.reflect.GeneratedMethodAccessor130.invoke(Unknown Source) at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
at java.lang.reflect.Method.invoke(Method.java:498) at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
 
at com.sun.proxy.$Proxy206.setup(Unknown Source) at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPipeline(AbstractProcessingPipeline.java:343)
 
at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:710)
 
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:466)
 
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.prepareInternal(AbstractProcessingPipeline.java:480)
 
at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source) at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
at java.lang.reflect.Method.invoke(Method.java:498) at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
 
at com.sun.proxy.$Proxy205.prepareInternal(Unknown Source) at 
org.apache.cocoon.components.source.impl.SitemapSource.init(SitemapSource.java:292)
 
at 

[dspace-tech] Re: XMLUI and Mirrage 2 theme

[eneshukic via DSpace Technical Support]

Hi Cristina,

Try to enable Javascript on your browser, then try again.  Also, did you 
install prerequisites: 
https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2 ?

Enes

On Tuesday, August 8, 2017 at 1:11:00 PM UTC+2, Cristina wrote:
>
> I have installed and configured Dspace 6.1 based on the installation 
> documentation. However, while the localhost:8080/jspui working, 
> localhost:8080/xmlui produces error message. 
>
>
> 
> Do you have any method to fix the problem? All other themes are fine.
>

-- 
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.