Re: [dspace-tech] oai and access restricted items

2016-01-21 Thread Jose Blanco 
Claudia.  I noticed that I was missing:
 DSpaceWithdrawnFilter.java
in dspace-oai/src/main/java/org/dspace/xoai/filter
so I copied the one from:
https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-oai/src/main/java/org/dspace/xoai/filter/DSpaceWithdrawnFilter.java

But now I see that all the other files in this directory are different from
the ones in this gihub repository.  I started off with 5.1 from a gz file.
I wonder what happened.  Should I just use all the files and directories
from the filter dir in github?

Thank you!
Jose

On Wed, Jan 20, 2016 at 5:15 PM, Jose Blanco  wrote:

> I have to go now but I think my problem is in the xoia.xml file.  I will
> change it tomorrow and see what happens.
>
> I'll let you know.
>
> -Jose
>
> On Wed, Jan 20, 2016 at 4:14 PM, Jose Blanco  wrote:
>
>> Claudia, I cant get to solr on the browser, put I put some debug
>> statements in the code and I can see that public is false for the item I'm
>> looking for as expected.
>>
>> 2016-01-20 16:01:35,475 INFO  org.dspace.xoai.app.XOAI @ Is Item Public
>> Jose = TEMP-BOGUS/236284 is false
>> 2016-01-20 16:01:35,477 INFO  org.dspace.xoai.app.XOAI @ OAI-Jose in
>> XOAI.java) processing handle = TEMP-BOGUS/236284
>> 2016-01-20 16:01:35,478 WARN  org.dspace.xoai.util.ItemUtils @
>> Authorization denied for action READ on BITSTREAM:563783 by user 0
>> org.dspace.authorize.AuthorizeException: Authorization denied for action
>> READ on BITSTREAM:563783 by user 0
>> at
>> org.dspace.authorize.AuthorizeManager.authorizeAction(AuthorizeManager.java:207)
>> at
>> org.dspace.authorize.AuthorizeManager.authorizeAction(AuthorizeManager.java:111)
>> at org.dspace.content.Bitstream.retrieve(Bitstream.java:604)
>> at org.dspace.xoai.util.ItemUtils.retrieveMetadata(ItemUtils.java:274)
>>
>> Where in the code does it check for public again? I'm using xoai.xml that
>> came with the 5.1 release. I have a feeling it's getting into solr with
>> public set to false, but that the code that retries it is ignoring the
>> setting.
>>
>> Thank you!
>> Jose
>>
>>
>> On Wed, Jan 20, 2016 at 8:55 AM, Claudia Jürgen <
>> claudia.juer...@tu-dortmund.de> wrote:
>>
>>> Hello Jose,
>>>
>>> you need not add this (unless you customized your xoai.xml and removed
>>> it or using another context). This is the default filter for the default
>>> context.
>>> Have you checked your oai solr data? The restricted item should have the
>>> field
>>> item.public set to false
>>>
>>>
>>> Claudia
>>>
>>>
>>>
>>> Am 19.01.2016 um 21:18 schrieb Jose Blanco:
>>>
 I just tried putting this:

  
  
  
  
  
  
  
  
  
  
  
  

 in xoai.xml

 but when I do oai/request?verb=Identify

 I get:

 2016-01-19 15:14:05,433 ERROR org.dspace.xoai.app.BasicConfiguration @
 Not
 able to start XOAI normal cache service.
 org.dspace.xoai.services.api.config.XOAIManagerResolverException:
 com.lyncode.xoai.dataprovider.exceptions.ConfigurationException:
 Unexpected
 element LeftCondition


 On Tue, Jan 19, 2016 at 4:04 AM, Claudia Jürgen <
 claudia.juer...@tu-dortmund.de> wrote:

 Hello Jose,
>
> I think the harvest.includedrestricted.oai dspace.cfg parameter is no
> longer valid since the xoai is in use.
> You can achieve it with xoai.xml setting. The default filter applied to
> the default context:
>
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>
> already contains an itemAccessCondition, which is based afair on the
> DEFAULT_ITEM_READ and not on the acutal rights.
>
> If you are using 5.1 and running
> [dspace]/bin/dspace oai import -c
> you might just be stuck with this error
> https://jira.duraspace.org/browse/DS-2543
> which was resolved in 5.3.
>
> Hope this helps
>
> Claudia Jürgen
>
>
>
>
> Am 18.01.2016 um 18:40 schrieb Jose Blanco:
>
> Going to re-post this question.
>>
>> -Jose
>>
>> On Wed, Jan 6, 2016 at 4:11 PM, Jose Blanco 
>> wrote:
>>
>> I tried it on 5.1.  I had an item that was completely restricted to a
>>
>>> group that was not Anonymous and I did:
>>>
>>> ./dspace oai -c import
>>>
>>> And the restricted item showed up.
>>>
>>> Do I need to make any changes to this file:
>>>
>>>
>>>
>>>
>>>

Re: [dspace-tech] oai and access restricted items

2016-01-21 Thread Claudia Jürgen 

Hello Jose,

per default you can access solr only from the machine it's runnning on.

You can forward the graphical output in order to use a browser or access
it with command line tools like curl.
Here are som examples:
gives you the number of all items which are not public
curl -g http://localhost:8080/solr/oai/select -d
'q=item.public:false=0=xml'

gives you the complete information of single item
curl -g http://localhost:8080/solr/oai/select -d
'q=item.id:YOURITEMID=1=xml'

So check the data in the solr oai core. If it is not correct run a full
import.

[dspace]/bin/dspace oai import -c

[dspace]/bin/dspace oai import without -c is an incremental import and
will only add new items to the index, but does not reflect changes to
existing items.

and then clean your cache by running
[dspace]/bin/dspace oai clean-cache
or manually remove the data under
[dspace]/var/oai/requests

there was an issue https://jira.duraspace.org/browse/DS-2543 which was
resolved in 5.3 where running
[dspace]/bin/dspace oai import -c did not clear the cache

Hope this helps

Claudia

Am 20.01.2016 um 22:14 schrieb Jose Blanco:

Claudia, I cant get to solr on the browser, put I put some debug statements
in the code and I can see that public is false for the item I'm looking for
as expected.

2016-01-20 16:01:35,475 INFO  org.dspace.xoai.app.XOAI @ Is Item Public
Jose = TEMP-BOGUS/236284 is false
2016-01-20 16:01:35,477 INFO  org.dspace.xoai.app.XOAI @ OAI-Jose in
XOAI.java) processing handle = TEMP-BOGUS/236284
2016-01-20 16:01:35,478 WARN  org.dspace.xoai.util.ItemUtils @
Authorization denied for action READ on BITSTREAM:563783 by user 0
org.dspace.authorize.AuthorizeException: Authorization denied for action
READ on BITSTREAM:563783 by user 0
at
org.dspace.authorize.AuthorizeManager.authorizeAction(AuthorizeManager.java:207)
at
org.dspace.authorize.AuthorizeManager.authorizeAction(AuthorizeManager.java:111)
at org.dspace.content.Bitstream.retrieve(Bitstream.java:604)
at org.dspace.xoai.util.ItemUtils.retrieveMetadata(ItemUtils.java:274)

Where in the code does it check for public again? I'm using xoai.xml that
came with the 5.1 release. I have a feeling it's getting into solr with
public set to false, but that the code that retries it is ignoring the
setting.

Thank you!
Jose


On Wed, Jan 20, 2016 at 8:55 AM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:


Hello Jose,

you need not add this (unless you customized your xoai.xml and removed
it or using another context). This is the default filter for the default
context.
Have you checked your oai solr data? The restricted item should have the
field
item.public set to false


Claudia



Am 19.01.2016 um 21:18 schrieb Jose Blanco:


I just tried putting this:

  
  
  
  
  
  
  
  
  
  
  
  

in xoai.xml

but when I do oai/request?verb=Identify

I get:

2016-01-19 15:14:05,433 ERROR org.dspace.xoai.app.BasicConfiguration @ Not
able to start XOAI normal cache service.
org.dspace.xoai.services.api.config.XOAIManagerResolverException:
com.lyncode.xoai.dataprovider.exceptions.ConfigurationException:
Unexpected
element LeftCondition


On Tue, Jan 19, 2016 at 4:04 AM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:

Hello Jose,

I think the harvest.includedrestricted.oai dspace.cfg parameter is no
longer valid since the xoai is in use.
You can achieve it with xoai.xml setting. The default filter applied to
the default context:

  
  
  
  
  
  
  
  
  
  
  
  
  

already contains an itemAccessCondition, which is based afair on the
DEFAULT_ITEM_READ and not on the acutal rights.

If you are using 5.1 and running
[dspace]/bin/dspace oai import -c
you might just be stuck with this error
https://jira.duraspace.org/browse/DS-2543
which was resolved in 5.3.

Hope this helps

Claudia Jürgen




Am 18.01.2016 um 18:40 schrieb Jose Blanco:

Going to re-post this question.

-Jose

On Wed, Jan 6, 2016 at 4:11 PM, Jose Blanco  wrote:

I tried it on 5.1.  I had an item that was completely restricted to a


group that was not Anonymous and I did:

./dspace oai -c import

And the restricted item showed up.

Do I need to make any changes to this file:




https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/xoai.xml#L51

Or should it just work by default.

Thank you!

On Thu, Dec 17, 2015 at 10:08 AM, helix84  wrote:

On Tue, Dec 15, 2015 at 5:10 PM, Jose Blanco 
wrote:


harvest.includerestricted.oai = false


I can't find where in the code it's used.

I couldn't find any uses, either.


We'll

Re: [dspace-tech] oai and access restricted items

2016-01-20 Thread Claudia Jürgen 

Hello Jose,

you need not add this (unless you customized your xoai.xml and removed
it or using another context). This is the default filter for the default
context.
Have you checked your oai solr data? The restricted item should have the
field
item.public set to false


Claudia


Am 19.01.2016 um 21:18 schrieb Jose Blanco:

I just tried putting this:

 
 
 
 
 
 
 
 
 
 
 
 

in xoai.xml

but when I do oai/request?verb=Identify

I get:

2016-01-19 15:14:05,433 ERROR org.dspace.xoai.app.BasicConfiguration @ Not
able to start XOAI normal cache service.
org.dspace.xoai.services.api.config.XOAIManagerResolverException:
com.lyncode.xoai.dataprovider.exceptions.ConfigurationException: Unexpected
element LeftCondition


On Tue, Jan 19, 2016 at 4:04 AM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:


Hello Jose,

I think the harvest.includedrestricted.oai dspace.cfg parameter is no
longer valid since the xoai is in use.
You can achieve it with xoai.xml setting. The default filter applied to
the default context:

 
 
 
 
 
 
 
 
 
 
 
 
 

already contains an itemAccessCondition, which is based afair on the
DEFAULT_ITEM_READ and not on the acutal rights.

If you are using 5.1 and running
[dspace]/bin/dspace oai import -c
you might just be stuck with this error
https://jira.duraspace.org/browse/DS-2543
which was resolved in 5.3.

Hope this helps

Claudia Jürgen




Am 18.01.2016 um 18:40 schrieb Jose Blanco:


Going to re-post this question.

-Jose

On Wed, Jan 6, 2016 at 4:11 PM, Jose Blanco  wrote:

I tried it on 5.1.  I had an item that was completely restricted to a

group that was not Anonymous and I did:

./dspace oai -c import

And the restricted item showed up.

Do I need to make any changes to this file:



https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/xoai.xml#L51

Or should it just work by default.

Thank you!

On Thu, Dec 17, 2015 at 10:08 AM, helix84  wrote:

On Tue, Dec 15, 2015 at 5:10 PM, Jose Blanco  wrote:

harvest.includerestricted.oai = false

I can't find where in the code it's used.

I couldn't find any uses, either.

We'll probably have to do a review of configuration properties for
DSpace
6, so I expect we'll deal with it there.


Is there any documentation on how to have oai not provide restricted

items?

Since DSpace 5.0, that should be the case by default (DS-1856). If it

isn't so, please, reopen that bug or file a new one.

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

Slightly related:

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


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.



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

Re: [dspace-tech] oai and access restricted items

2016-01-19 Thread Claudia Jürgen 

Hello Jose,

I think the harvest.includedrestricted.oai dspace.cfg parameter is no
longer valid since the xoai is in use.
You can achieve it with xoai.xml setting. The default filter applied to
the default context:















already contains an itemAccessCondition, which is based afair on the
DEFAULT_ITEM_READ and not on the acutal rights.

If you are using 5.1 and running
[dspace]/bin/dspace oai import -c
you might just be stuck with this error
https://jira.duraspace.org/browse/DS-2543
which was resolved in 5.3.

Hope this helps

Claudia Jürgen



Am 18.01.2016 um 18:40 schrieb Jose Blanco:

Going to re-post this question.

-Jose

On Wed, Jan 6, 2016 at 4:11 PM, Jose Blanco  wrote:


I tried it on 5.1.  I had an item that was completely restricted to a
group that was not Anonymous and I did:

./dspace oai -c import

And the restricted item showed up.

Do I need to make any changes to this file:


https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/xoai.xml#L51

Or should it just work by default.

Thank you!

On Thu, Dec 17, 2015 at 10:08 AM, helix84  wrote:


On Tue, Dec 15, 2015 at 5:10 PM, Jose Blanco  wrote:


harvest.includerestricted.oai = false

I can't find where in the code it's used.


I couldn't find any uses, either.
We'll probably have to do a review of configuration properties for DSpace
6, so I expect we'll deal with it there.



Is there any documentation on how to have oai not provide restricted
items?


Since DSpace 5.0, that should be the case by default (DS-1856). If it
isn't so, please, reopen that bug or file a new one.

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

Slightly related:

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


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.





--
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] oai and access restricted items

2016-01-19 Thread Jose Blanco 
I just tried putting this:














in xoai.xml

but when I do oai/request?verb=Identify

I get:

2016-01-19 15:14:05,433 ERROR org.dspace.xoai.app.BasicConfiguration @ Not
able to start XOAI normal cache service.
org.dspace.xoai.services.api.config.XOAIManagerResolverException:
com.lyncode.xoai.dataprovider.exceptions.ConfigurationException: Unexpected
element LeftCondition


On Tue, Jan 19, 2016 at 4:04 AM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:

> Hello Jose,
>
> I think the harvest.includedrestricted.oai dspace.cfg parameter is no
> longer valid since the xoai is in use.
> You can achieve it with xoai.xml setting. The default filter applied to
> the default context:
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> already contains an itemAccessCondition, which is based afair on the
> DEFAULT_ITEM_READ and not on the acutal rights.
>
> If you are using 5.1 and running
> [dspace]/bin/dspace oai import -c
> you might just be stuck with this error
> https://jira.duraspace.org/browse/DS-2543
> which was resolved in 5.3.
>
> Hope this helps
>
> Claudia Jürgen
>
>
>
>
> Am 18.01.2016 um 18:40 schrieb Jose Blanco:
>
>> Going to re-post this question.
>>
>> -Jose
>>
>> On Wed, Jan 6, 2016 at 4:11 PM, Jose Blanco  wrote:
>>
>> I tried it on 5.1.  I had an item that was completely restricted to a
>>> group that was not Anonymous and I did:
>>>
>>> ./dspace oai -c import
>>>
>>> And the restricted item showed up.
>>>
>>> Do I need to make any changes to this file:
>>>
>>>
>>>
>>> https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/xoai.xml#L51
>>>
>>> Or should it just work by default.
>>>
>>> Thank you!
>>>
>>> On Thu, Dec 17, 2015 at 10:08 AM, helix84  wrote:
>>>
>>> On Tue, Dec 15, 2015 at 5:10 PM, Jose Blanco  wrote:

 harvest.includerestricted.oai = false
>
> I can't find where in the code it's used.
>
> I couldn't find any uses, either.
 We'll probably have to do a review of configuration properties for
 DSpace
 6, so I expect we'll deal with it there.


 Is there any documentation on how to have oai not provide restricted
> items?
>
> Since DSpace 5.0, that should be the case by default (DS-1856). If it
 isn't so, please, reopen that bug or file a new one.

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

 Slightly related:

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


 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.


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

Re: [dspace-tech] oai and access restricted items

2016-01-06 Thread Jose Blanco 
I tried it on 5.1.  I had an item that was completely restricted to a group
that was not Anonymous and I did:

./dspace oai -c import

And the restricted item showed up.

Do I need to make any changes to this file:

https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/xoai.xml#L51

Or should it just work by default.

Thank you!

On Thu, Dec 17, 2015 at 10:08 AM, helix84  wrote:

> On Tue, Dec 15, 2015 at 5:10 PM, Jose Blanco  wrote:
>
>> harvest.includerestricted.oai = false
>>
>> I can't find where in the code it's used.
>>
>
> I couldn't find any uses, either.
> We'll probably have to do a review of configuration properties for DSpace
> 6, so I expect we'll deal with it there.
>
>
>> Is there any documentation on how to have oai not provide restricted
>> items?
>>
>
> Since DSpace 5.0, that should be the case by default (DS-1856). If it
> isn't so, please, reopen that bug or file a new one.
>
> https://jira.duraspace.org/browse/DS-1856
>
> Slightly related:
>
> https://jira.duraspace.org/browse/DS-950
>
>
> 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.