[dspace-tech] Re: Need help to configure tomcat

[Alex Yefimov]

Hi. I have no problems with installing tomcat, also i have no linux on the 
machine with tomcat. I have a problems with root base of nginx proxy or 
tomcat vhost.

понедельник, 17 апреля 2017 г., 20:49:25 UTC+5 пользователь Mónica Gabriela 
написал:
>
>
> Hi Alex
>
>I recomend this link: 
> http://idroot.net/tutorials/how-to-install-apache-tomcat-8-on-ubuntu-14-04/ 
>
>
>
>
>
>
> El viernes, 14 de abril de 2017, 15:04:30 (UTC-4:30), Alex Yefimov 
> escribió:
>>
>> Hi.
>>
>> I have a nginx on domain http://idun.urfu.ru and http proxy from 
>> http://idun.urfu.ru/sovietsociety to my dspace host in a private 
>> network. I have a good dspace.url and dspace.baseurl in dspace.cfg, but my 
>> tomcat shows http://idun.urfu.ru/sovietsociety as a root 
>> http://idun.urfu.ru/ :(
>>
>> What should I do with a tomcat or may be with dspace.cfg to make a good 
>> "root" and good absolute paths?
>>
>>
>>

-- 
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: How to change the orcid url in researcher page

[Lucas Rodrigues Costa]

Hello everyone!

I found where changes the ORCID url. 

Simply change the ORCID field on CRIS Module page->Resersher 
Page->Profile->Available fields->ORCID

I just change the last textbox (Custom Processing)

Thanks

Em terça-feira, 18 de abril de 2017 14:02:56 UTC-3, Lucas Rodrigues Costa 
escreveu:
>
> Hi everyone,
>
> Recently I put the orcid in my DSpace-CRIS and everything works, logs and 
> claims. However, I need change the orcid url in researcher page, and I 
> don't know how do it.
>
> The url of my DSpace-CRIS application: 
> https://coteccris.ibict.br/jspui/cris/rp/rp4
>
> I need change the ORCID field. In edit mode I put only the orcid ID and 
> the system put the sample url: 
> http://sandbox.orcid.org/-0002-0973-4866 but I need this url: 
> http://orcid.org/-0002-0973-4866
>
> Thank very much.
>

-- 
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] How to change the orcid url in researcher page

[Lucas Rodrigues Costa]

Hi everyone,

Recently I put the orcid in my DSpace-CRIS and everything works, logs and 
claims. However, I need change the orcid url in researcher page, and I 
don't know how do it.

The url of my DSpace-CRIS application: 
https://coteccris.ibict.br/jspui/cris/rp/rp4

I need change the ORCID field. In edit mode I put only the orcid ID and the 
system put the sample url: http://sandbox.orcid.org/-0002-0973-4866 but 
I need this url: http://orcid.org/-0002-0973-4866

Thank very much.

-- 
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: Items not visible when using IP authentication on an individual collection

[mark . gavillet]

Hi Claudia,

Thanks for this - I assumed I must be missing something obvious so it's 
nice to know I had everything set correctly!

Thanks
Mark

On Tuesday, 18 April 2017 11:56:03 UTC+1, mark.g...@ptfs-europe.com wrote:
>
> Hi,
>
> I've set up a collection within DSpace 6, enabled IP authentication, and 
> assigned a group to a collection. When accessing Dspace outside the IP 
> range nothing is visible, within the IP range I can see listings for items 
> within the collection.
>
> However, when I select an item and I'm within an authorised IP range I get 
> the message 'This item is restricted'.
>
> In local.cfg I have:
>
> plugin.sequence.org.dspace.authenticate/AuthenticationMethod = 
> org.dspace.authenticate.IPAuthentication
> plugin.sequence.org.dspace.authenticate/AuthenticationMethod = 
> org.dspace.authenticate.PasswordAuthentication
>
> (I've also tried switching this to authentication.cfg and have the same 
> problem)
>
> In authentication-ip.cfg I have:
>
> authentication-ip.TESTGROUP =  (obviously IP addresses set 
> here, not )
>
> DEFAULT_READ_ACCESS for the collection is assigned to TESTGROUP
>
> Does anyone have any idea why DSpace is restricting access to item view 
> within the collection?
>
> Thanks in advance,
> Mark
>

-- 
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: Items not visible when using IP authentication on an individual collection

[Claudia Jürgen]

Hi Mark,

you're right, just tested it on a 6.x instance.
The resource policies are set correctly, thus with rights access
awareness the items are listed for a user within the ip range, but still
a logged in user is needed.
Once logged in one can see that the user belongs to the ip defined group.
I created a Ticket:
https://jira.duraspace.org/browse/DS-3576

Claudia Jürgen


Am 18.04.2017 um 13:26 schrieb mark.gavil...@ptfs-europe.com:

Hi Claudia,

Thanks for your reply. DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ for the
collection is set for the group TESTGROUP and the items were added after
the authentication settings were applied. I've just checked the items in
the collection and READ is definitely set for each.

Thanks
Mark

On Tuesday, 18 April 2017 11:56:03 UTC+1, mark.g...@ptfs-europe.com wrote:

Hi,

I've set up a collection within DSpace 6, enabled IP authentication, and
assigned a group to a collection. When accessing Dspace outside the IP
range nothing is visible, within the IP range I can see listings for items
within the collection.

However, when I select an item and I'm within an authorised IP range I get
the message 'This item is restricted'.

In local.cfg I have:

plugin.sequence.org.dspace.authenticate/AuthenticationMethod =
org.dspace.authenticate.IPAuthentication
plugin.sequence.org.dspace.authenticate/AuthenticationMethod =
org.dspace.authenticate.PasswordAuthentication

(I've also tried switching this to authentication.cfg and have the same
problem)

In authentication-ip.cfg I have:

authentication-ip.TESTGROUP =  (obviously IP addresses set
here, not )

DEFAULT_READ_ACCESS for the collection is assigned to TESTGROUP

Does anyone have any idea why DSpace is restricting access to item view
within the collection?

Thanks in advance,
Mark



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

[dspace-tech] Re: Login authorization broken

[Donald Bynum]

Problem solved.  My own fault.  I had re-deployed and somehow had the 
autoregister set to true in the LDAP config file.

Best regards,

Don.

On Tuesday, April 18, 2017 at 8:32:16 AM UTC-4, Donald Bynum wrote:

> I am running DSpace 5.5 with XMLUI and Oracle.  I am seeing very unwanted 
> behavior when a user logs in.  Here are the details of my config:
>
> I am using LDAP authentication - that's appears to be working, in as much 
> as all users can login using their LDAP credentials.  The issue I am seeing 
> is as follows:
>
> I have a user who already has an eperson record with say eperson_id=100 
> and that eperson has an email address of b...@thing.org in the eperson 
> database record..  That eperson is assigned to various authorizations 
> (COllection Admins, etc.).  Whne that person authenticates via the login 
> page, what happens is that a brand new eperson record is created with 
> eperson_id=101, with just the userid in the eperson email column in the 
> eperson table, i.e. bob.  That new eperson, of course, has no 
> authorizations, since they were just created as a function of logging in.
>
> I have deleted via the UI, the original eperson record (the one with 
> b...@thing.org) with eperson_id-100 and also the newly created one with 
> eperson_id=101.  So, now that user has no eperson records.  I then ask that 
> user to try and login and it is successful with yet another simple eperson 
> record created (again with just bob in the email address and 
> eperson_id=102).
>
> What am I missing or what is mis-configured such that this is happening?
>
> Any help would be very much appreciated.
>
> Regards,
>
> Don Bynum
>

-- 
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 filtering with Solr queries

[Gonzalo Faramiñan]

Hi,

Dspace 4.1, Tomcat 7.0.65 , CentOS 6.8

I have created a new context and set successfully, even using transformers
and filters.

But I've just found a limitation using filters: I could only use *metadata*
filters, while I would like to populate this new set filtering the input
records by an *item.collections* Solr query. I've tried both
DspaceSetSpecFilter

and
SolrFilterResult

filters without success.

At dspace/config/modules/oai.cfg, "storage" parameter is set to "solr".

Any help is appreciated!

Gonzalo

-- 
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] Login authorization broken

[Donald Bynum]

I am running DSpace 5.5 with XMLUI and Oracle.  I am seeing very unwanted 
behavior when a user logs in.  Here are the details of my config:

I am using LDAP authentication - that's appears to be working, in as much 
as all users can login using their LDAP credentials.  The issue I am seeing 
is as follows:

I have a user who already has an eperson record with say eperson_id=100 and 
that eperson has an email address of b...@thing.org in the eperson database 
record..  That eperson is assigned to various authorizations (COllection 
Admins, etc.).  Whne that person authenticates via the login page, what 
happens is that a brand new eperson record is created with eperson_id=101, 
with just the userid in the eperson email column in the eperson table, i.e. 
bob.  That new eperson, of course, has no authorizations, since they were 
just created as a function of logging in.

I have deleted via the UI, the original eperson record (the one with 
b...@thing.org) with eperson_id-100 and also the newly created one with 
eperson_id=101.  So, now that user has no eperson records.  I then ask that 
user to try and login and it is successful with yet another simple eperson 
record created (again with just bob in the email address and 
eperson_id=102).

What am I missing or what is mis-configured such that this is happening?

Any help would be very much appreciated.

Regards,

Don Bynum

-- 
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: Items not visible when using IP authentication on an individual collection

[mark . gavillet]

Hi Claudia,

Thanks for your reply. DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ for the 
collection is set for the group TESTGROUP and the items were added after 
the authentication settings were applied. I've just checked the items in 
the collection and READ is definitely set for each.

Thanks
Mark

On Tuesday, 18 April 2017 11:56:03 UTC+1, mark.g...@ptfs-europe.com wrote:
>
> Hi,
>
> I've set up a collection within DSpace 6, enabled IP authentication, and 
> assigned a group to a collection. When accessing Dspace outside the IP 
> range nothing is visible, within the IP range I can see listings for items 
> within the collection.
>
> However, when I select an item and I'm within an authorised IP range I get 
> the message 'This item is restricted'.
>
> In local.cfg I have:
>
> plugin.sequence.org.dspace.authenticate/AuthenticationMethod = 
> org.dspace.authenticate.IPAuthentication
> plugin.sequence.org.dspace.authenticate/AuthenticationMethod = 
> org.dspace.authenticate.PasswordAuthentication
>
> (I've also tried switching this to authentication.cfg and have the same 
> problem)
>
> In authentication-ip.cfg I have:
>
> authentication-ip.TESTGROUP =  (obviously IP addresses set 
> here, not )
>
> DEFAULT_READ_ACCESS for the collection is assigned to TESTGROUP
>
> Does anyone have any idea why DSpace is restricting access to item view 
> within the collection?
>
> Thanks in advance,
> Mark
>

-- 
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] Items not visible when using IP authentication on an individual collection

[Claudia Jürgen]

Hello Mark,

during submission items and bitstreams derive their policies from the
collection settings:
DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ
If you change these settings, the change will only influence newly added
items. For existing items you got to use
the Advanced/Item Wildcard Policy Admin Tool

Have you checked the authorizations on the items in question?

Hope this helps

Claudia Jürgen



Am 18.04.2017 um 12:56 schrieb mark.gavil...@ptfs-europe.com:

Hi,

I've set up a collection within DSpace 6, enabled IP authentication, and
assigned a group to a collection. When accessing Dspace outside the IP
range nothing is visible, within the IP range I can see listings for items
within the collection.

However, when I select an item and I'm within an authorised IP range I get
the message 'This item is restricted'.

In local.cfg I have:

plugin.sequence.org.dspace.authenticate/AuthenticationMethod =
org.dspace.authenticate.IPAuthentication
plugin.sequence.org.dspace.authenticate/AuthenticationMethod =
org.dspace.authenticate.PasswordAuthentication

(I've also tried switching this to authentication.cfg and have the same
problem)

In authentication-ip.cfg I have:

authentication-ip.TESTGROUP =  (obviously IP addresses set here,
not )

DEFAULT_READ_ACCESS for the collection is assigned to TESTGROUP

Does anyone have any idea why DSpace is restricting access to item view
within the collection?

Thanks in advance,
Mark



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

[dspace-tech] Items not visible when using IP authentication on an individual collection

[mark . gavillet]

Hi,

I've set up a collection within DSpace 6, enabled IP authentication, and 
assigned a group to a collection. When accessing Dspace outside the IP 
range nothing is visible, within the IP range I can see listings for items 
within the collection.

However, when I select an item and I'm within an authorised IP range I get 
the message 'This item is restricted'.

In local.cfg I have:

plugin.sequence.org.dspace.authenticate/AuthenticationMethod = 
org.dspace.authenticate.IPAuthentication
plugin.sequence.org.dspace.authenticate/AuthenticationMethod = 
org.dspace.authenticate.PasswordAuthentication

(I've also tried switching this to authentication.cfg and have the same 
problem)

In authentication-ip.cfg I have:

authentication-ip.TESTGROUP =  (obviously IP addresses set here, 
not )

DEFAULT_READ_ACCESS for the collection is assigned to TESTGROUP

Does anyone have any idea why DSpace is restricting access to item view 
within the collection?

Thanks in advance,
Mark

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