Re: [dspace-tech] Embargo date can't be more than 3 years in the future?

[Paige Morgan]

Thanks, Sean! That does indeed seem to be what I needed.

Paige

-
*Meeting/regular work hours: Monday - Friday, 9am-4:30pm*

Dr. Paige C. Morgan
(she/they)
Digital Publishing and Copyright Librarian,
Head of Digital Initiatives & Preservation
University of Delaware Library, Museums and Press (on Lenape land
<https://native-land.ca/maps/territories/lenape/>)
Morris 118
ORCID: https://orcid.org/-0001-8076-7356
paig...@udel.edu
302.831.7153

Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings
available via Zoom, phone, etc.)
*** I observe email-free evenings and weekends. ***


On Wed, Sep 20, 2023 at 12:32 PM Sean Kalynuk 
wrote:

> Hi Paige,
>
>
>
> The relevant documentation you are looking for can be found here:
>
>
>
>
> https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface#SubmissionUserInterface-Modifyingaccessconditions(embargo,etc.)presentedforBitstreams
>
>
>
> --
>
> Sean
>
>
>
> *From: *dspace-tech@googlegroups.com  on
> behalf of Paige Morgan 
> *Date: *Wednesday, September 20, 2023 at 11:03 AM
> *To: *DSpace Technical Support 
> *Subject: *[dspace-tech] Embargo date can't be more than 3 years in the
> future?
>
> *Caution:* This message was sent from outside the University of Manitoba.
>
>
>
> Hi, all--
>
>
>
> We're running DSpace 7.4, and we recently ran into an issue when trying to
> set an embargo for an open-access version of a scholarly publication. The
> publication has a 48-month embargo, but the interface won't let us set an
> embargo date that is later than September 2026 (36 months).
>
>
>
> I thought this might be a local setting for us, but I found the same limit
> in the demo.dspace.org sandbox -- though I'm not finding any indication
> in the documentation <https://wiki.lyrasis.org/display/DSDOC7x/Embargo>
> that the 36-month limit is intentional. Is this a hard limit, or just a
> configuration setting that we need to change?
>
>
>
> Thanks in advance!
>
> Paige
>
>
>
> -
>
> *Meeting/regular work hours: Monday - Friday, 9am-4:30pm*
>
>
>
> *Dr. Paige C. Morgan*
>
> (she/they)
> Digital Publishing and Copyright Librarian,
> Head of Digital Initiatives & Preservation
> University of Delaware Library, Museums and Press (on Lenape land
> <https://native-land.ca/maps/territories/lenape/>)
> Morris 118
> ORCID: https://orcid.org/-0001-8076-7356
> paig...@udel.edu
> 302.831.7153
>
> Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings
> available via Zoom, phone, etc.)
> *** I observe email-free evenings and weekends. ***
>
>
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> ---
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVdkE-JXOacdoJh-JnkFjgneOq00MfYgEb%2BxvLsrojLG6fw%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVdkE-JXOacdoJh-JnkFjgneOq00MfYgEb%2BxvLsrojLG6fw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVd%3DoAz9Ab5c0w9EmdrhwTTigZE%2BDa4__WU1uTJa2osG_Zw%40mail.gmail.com.

Re: [dspace-tech] Embargo date can't be more than 3 years in the future?

[Sean Kalynuk]

Hi Paige,

The relevant documentation you are looking for can be found here:

https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface#SubmissionUserInterface-Modifyingaccessconditions(embargo,etc.)presentedforBitstreams

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Paige Morgan 
Date: Wednesday, September 20, 2023 at 11:03 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Embargo date can't be more than 3 years in the future?
Caution: This message was sent from outside the University of Manitoba.

Hi, all--

We're running DSpace 7.4, and we recently ran into an issue when trying to set 
an embargo for an open-access version of a scholarly publication. The 
publication has a 48-month embargo, but the interface won't let us set an 
embargo date that is later than September 2026 (36 months).

I thought this might be a local setting for us, but I found the same limit in 
the demo.dspace.org<http://demo.dspace.org> sandbox -- though I'm not finding 
any indication in the 
documentation<https://wiki.lyrasis.org/display/DSDOC7x/Embargo> that the 
36-month limit is intentional. Is this a hard limit, or just a configuration 
setting that we need to change?

Thanks in advance!
Paige

-
Meeting/regular work hours: Monday - Friday, 9am-4:30pm


Dr. Paige C. Morgan
(she/they)
Digital Publishing and Copyright Librarian,
Head of Digital Initiatives & Preservation
University of Delaware Library, Museums and Press (on Lenape 
land<https://native-land.ca/maps/territories/lenape/>)
Morris 118
ORCID: https://orcid.org/-0001-8076-7356
paig...@udel.edu<mailto:paig...@udel.edu>
302.831.7153

Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings 
available via Zoom, phone, etc.)
** I observe email-free evenings and weekends. **

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVdkE-JXOacdoJh-JnkFjgneOq00MfYgEb%2BxvLsrojLG6fw%40mail.gmail.com<https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVdkE-JXOacdoJh-JnkFjgneOq00MfYgEb%2BxvLsrojLG6fw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YQBPR01MB10515B89516E9807928265705E8F9A%40YQBPR01MB10515.CANPRD01.PROD.OUTLOOK.COM.

[dspace-tech] Embargo date can't be more than 3 years in the future?

[Paige Morgan]

Hi, all--

We're running DSpace 7.4, and we recently ran into an issue when trying to
set an embargo for an open-access version of a scholarly publication. The
publication has a 48-month embargo, but the interface won't let us set an
embargo date that is later than September 2026 (36 months).

I thought this might be a local setting for us, but I found the same limit
in the demo.dspace.org sandbox -- though I'm not finding any indication in
the documentation  that
the 36-month limit is intentional. Is this a hard limit, or just a
configuration setting that we need to change?

Thanks in advance!
Paige

-
*Meeting/regular work hours: Monday - Friday, 9am-4:30pm*

Dr. Paige C. Morgan
(she/they)
Digital Publishing and Copyright Librarian,
Head of Digital Initiatives & Preservation
University of Delaware Library, Museums and Press (on Lenape land
)
Morris 118
ORCID: https://orcid.org/-0001-8076-7356
paig...@udel.edu
302.831.7153

Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings
available via Zoom, phone, etc.)
*** I observe email-free evenings and weekends. ***

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVdkE-JXOacdoJh-JnkFjgneOq00MfYgEb%2BxvLsrojLG6fw%40mail.gmail.com.

[dspace-tech] Embargo Until specific data:

[Daan Lessing]

Good day,

I have recently upgraded from Dspace 5.5 to version 6.3. When clicking on 
Edit Bitstream, the input box is greyed out for Embargo date setter and 
shows the message 
*Embargo until specific date:*
*xmlui.administrative.authorization.AccessStep.label_date_displayonly_help[image:
 
Screenshot 2022-04-26 at 12.44.45.png]*
Please can someone assist with this. It is supposed to show and display a 
pop up where you can set the date.

*Embargo until specific date:*
*The first day from which access is allowed. Accepted format: , 
-mm, -mm-dd*

Kind regards,
Daan

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/46d7cb22-ac01-410c-82f8-a1aace679d44n%40googlegroups.com.

[dspace-tech] Embargo date in dspace7.1

[sunit...@gmail.com]

While testing dspace 7.1 for adding embargo date in item metadata or 
bitstream the date entered gets automatically disappeared.

reg

Sunita Barve

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/f972ff90-aefa-4246-988a-7b36b5791858n%40googlegroups.com.

[dspace-tech] Embargo

[Saul hernandez ocadiz]

 Good afternoon! 
I have a question about the embargo period of an item, what is the maximum 
date that a embargo period can be allowed? 100 years? what is the maximum 
time allowed in the capture of an embargo period. Thank you so much! 

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/c6e365d2-4378-48d6-b5cb-202ed0f1cfcfn%40googlegroups.com.

[dspace-tech] embargo and import in 6.3

[Jose Blanco]

I just tried using the embargo functionality via the import script and I
see that the bitstreams are embargoed as I expected, but the item itself is
not private.  Is there a way to indicate to make the item private when
using the import script for items I want to put in embargo.  I'm assuming
that once the embargo period expires, the item will no longer be private.
Is that right?

Thank you!
-Jose

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-sdQ-MYQWU2fcnVTJji-_D5BQZW%3D3ONBw82c_u-LafaHA%40mail.gmail.com.

Re: [dspace-tech] Embargo Feature Does Not Work

[Tim Donohue]

Hello Herminarto,

As noted in my previous email, I'd recommend looking at how the embargo is
set on the item and checking to see if errors are displayed in your log
files (when you set a new embargo).  It's possible the date format is a
problem, but it's also possible something else is going on here.  I'm
hoping additional clues can help us (on this list) figure out how to help
you.

So, again, you might want to look more closely at the "start_date" set on
the policy for the embargoed Item.  Embargoes in DSpace essentially act as
an access policy that doesn't trigger until a particular date has passed.
You can see that "start_date" in the Admin Edit Item screens.  Here's a
guide on where to find this information:
https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-ManagingEmbargoesonexistingItems

I've just retested this feature on our Demo site (
http://demo.dspace.org/xmlui/), which is also running DSpace 6.3.  The date
should work under any of those formats (the text there looks to be slightly
incorrect).  So, the formats , -MM, -MM-DD *and* MM/DD/ are
all acceptable date formats.  I also verified that if I submit a document
on the demo site, and set an embargo date of 03/31/2019 (March 31, 2019),
then the embargo takes effect immediately.  If I logout and attempt to
access the newly embargoed item, then I am sent to a page that says "This
item is restricted".

Here's the Item that I just submitted and embargoed:
http://demo.dspace.org/xmlui/handle/10673/224  If you login as the Demo
Administrator (email:  dspacedemo+ad...@gmail.com , password: dspace) then
you will be able to see that item.  But, as an anonymous user, you'll see
the "This item is restricted" page.

So, I'm not sure exactly what could be happening on your local instance.
I'd recommend checking your logs for errors and also verify that the
"start_date" is being set to the embargo date on the Item policies.  Maybe
there will be clues available there that could help us all figure out the
problem.

Good luck,
Tim


On Thu, Feb 28, 2019 at 8:34 PM Herminarto Nugroho <
herminarto.nugr...@gmail.com> wrote:

> Hi Tim,
>
> Thanks for the reply.
>
> I am attempting to access the file after logging out (it means I am
> anonymous), and still able to access the file.
>
> Indeed, as an Admin I can modify the access policy of an existing file
> such that that particular item can only be accessed after a certain date.
>
> The problem is when the user wants to submit new files, and decided to set
> the embargo feature ON, the embargo feature in the submission process does
> not work well. I assume the problem is in the format of the date, but I am
> not sure. When I tried to submit a file and set the embargo,the date format
> does not match the accepted format. as you can see in the attached figure.
>
> Then I try to use JSPUI as well. The embargo still does not work, and even
> I cannot specify the date at all.
>
> [image: Screenshot_2.jpg]
> Best regards,
>
> Herminarto
>
> Pada Kamis, 28 Februari 2019 23.51.37 UTC+7, Tim Donohue menulis:
>>
>> Hello Herminarto,
>>
>> I'm not sure if this is the problem, but is it possible that you are
>> attempting to access the embargoed item *while you are logged in as an
>> Administrator*?
>>
>> Embargoes should take effect immediately. However, Administrative users
>> are *not* subject to those embargoes, and they will still be able to
>> download the items while they are logged in.  All other logged in users
>> (and anonymous users) should not be able to download the item.
>>
>> If this is not the problem, you might want to look more closely at the
>> "start_date" set on the policy for the embargoed Item.  Embargoes in DSpace
>> essentially act as an access policy that doesn't trigger until a particular
>> date has passed. You can see that "start_date" in the Admin Edit Item
>> screens.  Here's a guide on where to find this information:
>> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-ManagingEmbargoesonexistingItems
>>
>> You also might want to verify in the DSpace logs that no errors are
>> occurring when you assign the embargo to a new Item.
>>
>> Please report back on this mailing list with anything you find or if you
>> discover what the problem is.
>>
>> Thanks,
>>
>> Tim
>>
>>
>> On Thu, Feb 28, 2019 at 7:24 AM Herminarto Nugroho <
>> herminart...@gmail.com> wrote:
>>
>>> Dear all,
>>>
>>> I tried to enable the embargo feature by following the instruction from
>>> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-SimpleEmbargoSettings
>>> .
>>> I am using dspace 6.3 with xmlui. It seems everything's going ok, but
>>> when I try to submit a document with embargo, I specified the date the
>>> embargo should be lifted long way on the future, my document can still be
>>> downloaded freely right after my submission complete (which means the
>>> embargo does not work). When I see the column in which I mention embargo
>>> until specific date, it seems the date format

Re: [dspace-tech] Embargo Feature Does Not Work

[Herminarto Nugroho]

Hi Tim,

Thanks for the reply.

I am attempting to access the file after logging out (it means I am 
anonymous), and still able to access the file.

Indeed, as an Admin I can modify the access policy of an existing file such 
that that particular item can only be accessed after a certain date.

The problem is when the user wants to submit new files, and decided to set 
the embargo feature ON, the embargo feature in the submission process does 
not work well. I assume the problem is in the format of the date, but I am 
not sure. When I tried to submit a file and set the embargo,the date format 
does not match the accepted format. as you can see in the attached figure.

Then I try to use JSPUI as well. The embargo still does not work, and even 
I cannot specify the date at all.

[image: Screenshot_2.jpg] 
Best regards,

Herminarto

Pada Kamis, 28 Februari 2019 23.51.37 UTC+7, Tim Donohue menulis:
>
> Hello Herminarto,
>
> I'm not sure if this is the problem, but is it possible that you are 
> attempting to access the embargoed item *while you are logged in as an 
> Administrator*?
>
> Embargoes should take effect immediately. However, Administrative users 
> are *not* subject to those embargoes, and they will still be able to 
> download the items while they are logged in.  All other logged in users 
> (and anonymous users) should not be able to download the item.
>
> If this is not the problem, you might want to look more closely at the 
> "start_date" set on the policy for the embargoed Item.  Embargoes in DSpace 
> essentially act as an access policy that doesn't trigger until a particular 
> date has passed. You can see that "start_date" in the Admin Edit Item 
> screens.  Here's a guide on where to find this information: 
> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-ManagingEmbargoesonexistingItems
>
> You also might want to verify in the DSpace logs that no errors are 
> occurring when you assign the embargo to a new Item.
>
> Please report back on this mailing list with anything you find or if you 
> discover what the problem is.
>
> Thanks,
>
> Tim
>
>
> On Thu, Feb 28, 2019 at 7:24 AM Herminarto Nugroho  > wrote:
>
>> Dear all,
>>
>> I tried to enable the embargo feature by following the instruction from 
>> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-SimpleEmbargoSettings
>>  
>> .
>> I am using dspace 6.3 with xmlui. It seems everything's going ok, but 
>> when I try to submit a document with embargo, I specified the date the 
>> embargo should be lifted long way on the future, my document can still be 
>> downloaded freely right after my submission complete (which means the 
>> embargo does not work). When I see the column in which I mention embargo 
>> until specific date, it seems the date format is not accepted. Is that 
>> really the cause? How can I solve this problem?
>>
>> Best regards,
>>
>> Herminarto Nugroho
>>
>> -- 
>> 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+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] Embargo Feature Does Not Work

[Tim Donohue]

Hello Herminarto,

I'm not sure if this is the problem, but is it possible that you are
attempting to access the embargoed item *while you are logged in as an
Administrator*?

Embargoes should take effect immediately. However, Administrative users are
*not* subject to those embargoes, and they will still be able to download
the items while they are logged in.  All other logged in users (and
anonymous users) should not be able to download the item.

If this is not the problem, you might want to look more closely at the
"start_date" set on the policy for the embargoed Item.  Embargoes in DSpace
essentially act as an access policy that doesn't trigger until a particular
date has passed. You can see that "start_date" in the Admin Edit Item
screens.  Here's a guide on where to find this information:
https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-ManagingEmbargoesonexistingItems

You also might want to verify in the DSpace logs that no errors are
occurring when you assign the embargo to a new Item.

Please report back on this mailing list with anything you find or if you
discover what the problem is.

Thanks,

Tim


On Thu, Feb 28, 2019 at 7:24 AM Herminarto Nugroho <
herminarto.nugr...@gmail.com> wrote:

> Dear all,
>
> I tried to enable the embargo feature by following the instruction from
> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-SimpleEmbargoSettings
> .
> I am using dspace 6.3 with xmlui. It seems everything's going ok, but when
> I try to submit a document with embargo, I specified the date the embargo
> should be lifted long way on the future, my document can still be
> downloaded freely right after my submission complete (which means the
> embargo does not work). When I see the column in which I mention embargo
> until specific date, it seems the date format is not accepted. Is that
> really the cause? How can I solve this problem?
>
> Best regards,
>
> Herminarto Nugroho
>
> --
> 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.
>


-- 

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+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] Embargo Feature Does Not Work

[Herminarto Nugroho]

Dear all,

I tried to enable the embargo feature by following the instruction from 
https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-SimpleEmbargoSettings
 
.
I am using dspace 6.3 with xmlui. It seems everything's going ok, but when 
I try to submit a document with embargo, I specified the date the embargo 
should be lifted long way on the future, my document can still be 
downloaded freely right after my submission complete (which means the 
embargo does not work). When I see the column in which I mention embargo 
until specific date, it seems the date format is not accepted. Is that 
really the cause? How can I solve this problem?

Best regards,

Herminarto Nugroho

-- 
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] Embargo via Metadata

[Alejandro Castellanos Alvarez]

Hi everybody.
I have an issue when i implemented: Setting Embargo terms via metadata . 
The issues appears when  the submission step ends (Accept license) and 
previously i put liftdate ( embargo.field.lift = dc.embargo.liftdate)  :

   -  In JSPUI: show Internal Server Error, but the submission task is 
   completed (I see the item in the collection with embargo in metadatos and 
   bitstreams).


   - In XMLUI: show Internal Server Error but the submission does not 
   complete. 

This option is using the DefaultEmbargoSetter.
The print error stack is :
Java stacktrace: 
java.lang.NullPointerException
at 
org.dspace.embargo.DefaultEmbargoSetter.setEmbargo(DefaultEmbargoSetter.java:97)
at 
org.dspace.embargo.EmbargoServiceImpl.setEmbargo(EmbargoServiceImpl.java:103)
at 
org.dspace.content.InstallItemServiceImpl.finishItem(InstallItemServiceImpl.java:236)
at 
org.dspace.content.InstallItemServiceImpl.installItem(InstallItemServiceImpl.java:80)
at 
org.dspace.content.InstallItemServiceImpl.installItem(InstallItemServiceImpl.java:56)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.archive(BasicWorkflowServiceImpl.java:790)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.doState(BasicWorkflowServiceImpl.java:530)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.advance(BasicWorkflowServiceImpl.java:412)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.pool(BasicWorkflowServiceImpl.java:732)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.doState(BasicWorkflowServiceImpl.java:517)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.advance(BasicWorkflowServiceImpl.java:397)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.pool(BasicWorkflowServiceImpl.java:732)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.doState(BasicWorkflowServiceImpl.java:510)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.advance(BasicWorkflowServiceImpl.java:379)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.pool(BasicWorkflowServiceImpl.java:732)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.doState(BasicWorkflowServiceImpl.java:503)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.advance(BasicWorkflowServiceImpl.java:361)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.advance(BasicWorkflowServiceImpl.java:333)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.start(BasicWorkflowServiceImpl.java:257)
at 
org.dspace.workflowbasic.BasicWorkflowServiceImpl.start(BasicWorkflowServiceImpl.java:58)
at 
org.dspace.submit.step.CompleteStep.doProcessing(CompleteStep.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155)
at 
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243)
at 
org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237)
at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394)
at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162)
at 
org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393)
at 
org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834)
at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160)
at org.mozilla.javascript.Context.call(Context.java:538)
at 
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833)
at 
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1803)
at 
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:698)
at 
org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:94)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:82)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
at 
org.ap

Re: [dspace-tech] embargo

[Manjunath Sajjan]

Great, thanks for the info!

On Thu 17 May, 2018 00:09 Tim Donohue,  wrote:

> Hi Manjunath:
>
> Assuming you are using a recent version of DSpace (I believe this works
> in  4.x or above), the Embargo date can be managed by editing the Item's
> "Authorization Policies".  This is described (very briefly) here:
>
> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-DSpaceEmbargoFunctionality
>
> Here's how you'd do that (these are for the XMLUI, but similar options are
> available in JSPUI)
> 1) Login as an Admin
> 2) Browse to the embargoed item (Admins should be able to see any
> embargoed items)
> 3) Click on "Edit Item"
> 4) On the "Item Status" tab, click the "Authorizations" button
> 5) You'll then see a detailed list of all access policies on this item.
> Embargoes appear as *start dates* for a policy.  So, for example, if an
> Item is to become public *after January 1, 2020, you'll see a policy that
> says "Anonymous" access on 2020-01-01.
>
> To remove an embargo, click on the Policy to edit it, and clear out the
> "start date".
> To change an embargo, click on the Policy to edit it, and change the
> "start date" to a new date.
> To add an embargo, click on the Policy to edit it, and set a "start date".
>
> The change should take effect immediately.  Of course, as an Admin, you
> will have access to embargoed items. But, if you logout, the embargo should
> appear immediately.
>
> I hope that helps,
>
> Tim
>
> On Wed, May 16, 2018 at 12:43 PM George Kozak  wrote:
>
>> Manjunath:
>>
>> I am not sure if this is the best way to do this, but we at Cornell
>> University, we do this manually by going into the Postgres database and
>> manipulating the Resource Policy table.
>> Here is a simplified version of our procedure:
>>
>> To embargo an item, after submission:
>>- As Admin, go to edit an item and put the embargo date in the
>> dublin_core field that you are using for embargoes.
>>- Get the ID for the bitstream(s) that you want to embargo.
>>- Go to psql
>>   -select start_date from resourcepolicy where resource_id=> id>;
>>- Once you’ve determined that you found the correct bitstream and
>> date, you can execute:
>>   - update resorcepolicy set start_date= where
>> resource_id=;
>>- This has to be done for every bitstream that the item contains.
>>
>> To revise the embargo on an item:
>>  - Do the same as above
>>
>> To lift an embargo on an item:
>>  - Modify the dublin_core embargo field as described above, and find the
>> bitstream ids
>>  - Go to psql
>> - select start_date from resourcepolicy where resource_id=> id>;
>>  - Once you’ve determined that you found the correct bitstream and date,
>> you can execute:
>> - update resorcepolicy set start_date=null where
>> resource_id=;
>>
>> George Kozak
>> Cornell University
>>
>> On Tue, May 15, 2018 at 8:23 AM, Manjunath Sajjan 
>> wrote:
>>
>>> I would like to know even if it is possible to change the date of an
>>> embargo on an item after that it is submitted. And add/remove embargo
>>> date. How to achieve these?.
>>>
>>>
>>>
>>>
>>> __
>>>
>>> Best Regards,
>>> Manjunath Sajjan
>>>
>>> --
>>> 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.
>>>
>>
>>
>>
>> --
>> ***
>> George Kozak
>> Digital Library Specialist
>> Cornell University Library - IT
>> 218 Olin Library
>> Cornell University
>> Ithaca, NY 14853
>> 607-255-8924 <(607)%20255-8924>
>> g...@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.
>>
> --
> 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.

Re: [dspace-tech] embargo

[Tim Donohue]

Hi Manjunath:

Assuming you are using a recent version of DSpace (I believe this works in
4.x or above), the Embargo date can be managed by editing the Item's
"Authorization Policies".  This is described (very briefly) here:
https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-DSpaceEmbargoFunctionality

Here's how you'd do that (these are for the XMLUI, but similar options are
available in JSPUI)
1) Login as an Admin
2) Browse to the embargoed item (Admins should be able to see any embargoed
items)
3) Click on "Edit Item"
4) On the "Item Status" tab, click the "Authorizations" button
5) You'll then see a detailed list of all access policies on this item.
Embargoes appear as *start dates* for a policy.  So, for example, if an
Item is to become public *after January 1, 2020, you'll see a policy that
says "Anonymous" access on 2020-01-01.

To remove an embargo, click on the Policy to edit it, and clear out the
"start date".
To change an embargo, click on the Policy to edit it, and change the "start
date" to a new date.
To add an embargo, click on the Policy to edit it, and set a "start date".

The change should take effect immediately.  Of course, as an Admin, you
will have access to embargoed items. But, if you logout, the embargo should
appear immediately.

I hope that helps,

Tim

On Wed, May 16, 2018 at 12:43 PM George Kozak  wrote:

> Manjunath:
>
> I am not sure if this is the best way to do this, but we at Cornell
> University, we do this manually by going into the Postgres database and
> manipulating the Resource Policy table.
> Here is a simplified version of our procedure:
>
> To embargo an item, after submission:
>- As Admin, go to edit an item and put the embargo date in the
> dublin_core field that you are using for embargoes.
>- Get the ID for the bitstream(s) that you want to embargo.
>- Go to psql
>   -select start_date from resourcepolicy where resource_id= id>;
>- Once you’ve determined that you found the correct bitstream and date,
> you can execute:
>   - update resorcepolicy set start_date= where
> resource_id=;
>- This has to be done for every bitstream that the item contains.
>
> To revise the embargo on an item:
>  - Do the same as above
>
> To lift an embargo on an item:
>  - Modify the dublin_core embargo field as described above, and find the
> bitstream ids
>  - Go to psql
> - select start_date from resourcepolicy where resource_id= id>;
>  - Once you’ve determined that you found the correct bitstream and date,
> you can execute:
> - update resorcepolicy set start_date=null where
> resource_id=;
>
> George Kozak
> Cornell University
>
> On Tue, May 15, 2018 at 8:23 AM, Manjunath Sajjan 
> wrote:
>
>> I would like to know even if it is possible to change the date of an
>> embargo on an item after that it is submitted. And add/remove embargo
>> date. How to achieve these?.
>>
>>
>>
>>
>> __
>>
>> Best Regards,
>> Manjunath Sajjan
>>
>> --
>> 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.
>>
>
>
>
> --
> ***
> George Kozak
> Digital Library Specialist
> Cornell University Library - IT
> 218 Olin Library
> Cornell University
> Ithaca, NY 14853
> 607-255-8924 <(607)%20255-8924>
> g...@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.
>
-- 
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.

Re: [dspace-tech] embargo

[George Kozak]

Manjunath:

I am not sure if this is the best way to do this, but we at Cornell
University, we do this manually by going into the Postgres database and
manipulating the Resource Policy table.
Here is a simplified version of our procedure:

To embargo an item, after submission:
   - As Admin, go to edit an item and put the embargo date in the
dublin_core field that you are using for embargoes.
   - Get the ID for the bitstream(s) that you want to embargo.
   - Go to psql
  -select start_date from resourcepolicy where resource_id=;
   - Once you’ve determined that you found the correct bitstream and date,
you can execute:
  - update resorcepolicy set start_date= where
resource_id=;
   - This has to be done for every bitstream that the item contains.

To revise the embargo on an item:
 - Do the same as above

To lift an embargo on an item:
 - Modify the dublin_core embargo field as described above, and find the
bitstream ids
 - Go to psql
- select start_date from resourcepolicy where resource_id=;
 - Once you’ve determined that you found the correct bitstream and date,
you can execute:
- update resorcepolicy set start_date=null where resource_id=;

George Kozak
Cornell University

On Tue, May 15, 2018 at 8:23 AM, Manjunath Sajjan 
wrote:

> I would like to know even if it is possible to change the date of an
> embargo on an item after that it is submitted. And add/remove embargo
> date. How to achieve these?.
>
>
>
>
> __
>
> Best Regards,
> Manjunath Sajjan
>
> --
> 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.
>



-- 
***
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
g...@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] embargo

[Manjunath Sajjan]

 I would like to know even if it is possible to change the date of an
embargo on an item after that it is submitted. And add/remove embargo date.
How to achieve these?.




__

Best Regards,
Manjunath Sajjan

-- 
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] Embargo items in repository

[Rohit Patil]

We are running DSpace 5.6 and we would like to know what are the best 
methods to embargo 
1. item bitstreams until specific date
2. entire item (metadata and item bitstreams) until specific date

The bitstreams/items we embargo are critical (patents being applied or soon 
submitted to journal) and i wanted to make sure the method is safe and will 
not make anything public until embargo date. I guess the last option would 
be to not upload them but i wanted to check what method is followed by 
other users for hiding critical data.

Please suggest.




-- 
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] Embargo migration from one server to another

[aade13]

Hello,

Is there a way I can migrate embargo on a server running dspace 1.6 to 
another server running dspace 5.7?

The database and assetstore were transferred from the old server running 
dspace 1.6 to a new server and the documentation on how to upgrade was 
followed.

Then the new server was upgraded from dspace version 1.6 to 5.7 and the 
upgrade was done through every version. 

The new server running on dspace version 5.7 works but there are embargo 
dates set on the collections in the old server running version 1.6 missing 
on the new server running version 5.7, is there a way I can migrate the 
embargo with their policies from the old dspace server running version 1.6?

I will appreciate any assistance.

Thanks, Ade.

-- 
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] Embargo feature in DSpace 6.0+Mirage2

[Sunita Barve]

Hi all

Is there any issue with Embargo and DSpace 6.0 with Mirage2 theme. Even if 
embargo is enabled I can still open and see item with full text.

reg

Sunita Barve

-- 
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] Embargo date view

[Massimiliano CILURZO]

Dear Deborah,
   We do the embargo on the full text but how do you put a note on the 
bitstream to display the end of the embargo date?
Thanks
Best regards
Massimiliano

On Thursday, March 9, 2017 at 10:42:24 PM UTC+1, Fitchett, Deborah wrote:
>
> Dear Massimiliano,
>
>  
>
> Our solution may not work for you: for us, we don’t need to embargo the 
> metadata, only the full-text. So we don’t embargo the item at all, we only 
> embargo the bitstream. We also add a display note to the bitstream which 
> includes the embargo end-date.
>
>  
>
> Deborah
>
>  
>
> *From:* dspac...@googlegroups.com  [mailto:
> dspac...@googlegroups.com ] *On Behalf Of *Massimiliano 
> CILURZO
> *Sent:* Friday, 10 March 2017 5:05 a.m.
> *To:* DSpace Technical Support >
> *Subject:* [dspace-tech] Embargo date view
>
>  
>
> Dear All, 
>
>   We would like to show to the user when the embargo ends on an item.
>
> Normally the user see the item on the search result and when click on an 
> item with embargo the system tells to login.
>
> But this is wrong, because users can't see an item with embargo.
>
> So how you solved this problem?
>
> Thanks
>
> Best regards
>
> Massimiliano
>
> -- 
> 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.
> --
>
> P Please consider the environment before you print this email.
> "The contents of this e-mail (including any attachments) may be 
> confidential and/or subject to copyright. Any unauthorised use, 
> distribution, or copying of the contents is expressly prohibited. If you 
> have received this e-mail in error, please advise the sender by return 
> e-mail or telephone and then delete this e-mail together with all 
> attachments from your system." 
>

-- 
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] Embargo date view

[Fitchett, Deborah]

Dear Massimiliano,

Our solution may not work for you: for us, we don’t need to embargo the 
metadata, only the full-text. So we don’t embargo the item at all, we only 
embargo the bitstream. We also add a display note to the bitstream which 
includes the embargo end-date.

Deborah

From: dspace-tech@googlegroups.com [mailto:dspace-tech@googlegroups.com] On 
Behalf Of Massimiliano CILURZO
Sent: Friday, 10 March 2017 5:05 a.m.
To: DSpace Technical Support 
Subject: [dspace-tech] Embargo date view

Dear All,
  We would like to show to the user when the embargo ends on an item.
Normally the user see the item on the search result and when click on an item 
with embargo the system tells to login.
But this is wrong, because users can't see an item with embargo.
So how you solved this problem?
Thanks
Best regards
Massimiliano
--
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<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to 
dspace-tech@googlegroups.com<mailto: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.

P Please consider the environment before you print this email.
"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."

-- 
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] Embargo date view

[Massimiliano CILURZO]

Dear All,
  We would like to show to the user when the embargo ends on an item.
Normally the user see the item on the search result and when click on an 
item with embargo the system tells to login.
But this is wrong, because users can't see an item with embargo.
So how you solved this problem?
Thanks
Best regards
Massimiliano

-- 
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] Embargo not working after upgrade

[Javier Távara]

Hello, some time ago I updated a repository from 3.2 to 5.5 and everything 
was working fine until I tested some embargoed items.

I use this config:

 Embargo Settings 
# DC metadata field to hold the user-supplied embargo terms
embargo.field.terms = dc.embargo.terms

# DC metadata field to hold computed "lift date" of embargo
embargo.field.lift = dc.embargo.lift

# string in terms field to indicate indefinite embargo
embargo.terms.open = forever

# implementation of embargo setter plugin - replace with local 
implementation if applicable
plugin.single.org.dspace.embargo.EmbargoSetter = org.dspace.embargo.
DefaultEmbargoSetter

# implementation of embargo lifter plugin - - replace with local 
implementation if applicable
plugin.single.org.dspace.embargo.EmbargoLifter = org.dspace.embargo.
DefaultEmbargoLifter

Then I realized the dc.embargo.lift field it's computed correctly but *the 
bitstreams are still available to everyone.*

Running ./dspace embargo-lifter -a  manually seems to apply the 
restrictions.

I think this is not the correct behavior. How to do this automatically?

Thank you.
Javier T.

-- 
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] Embargo settings

[Fitchett, Deborah]

Kia ora koutou,

We’re starting to play with the embargo functionality, in v5.6 XMLUI (Mirage) – 
but to complicate matters most of our items are submitted from Symplectic 
Elements. It may turn out that we have to do a lot manually but first I want to 
test what we can do automatically and I’m running into some Unexpected 
Behaviour.

Our dspace.cfg embargo settings are:

 Embargo Settings 
# DC metadata field to hold the user-supplied embargo terms
embargo.field.terms = lu.embargo.ends

# DC metadata field to hold computed "lift date" of embargo
embargo.field.lift = lu.embargo.enddate

# string in terms field to indicate indefinite embargo
embargo.terms.open = forever
embargo.terms.days = 3 months:91,6 months:182,9 months:274,12 months:365,1 
year:365,15 months:456,18 months:548,21 months:639,24 months:730

# implementation of embargo setter plugin - replace with local implementation 
if applicable
plugin.single.org.dspace.embargo.EmbargoSetter = 
org.dspace.embargo.DefaultEmbargoSetter

# implementation of embargo lifter plugin - - replace with local implementation 
if applicable
plugin.single.org.dspace.embargo.EmbargoLifter = 
org.dspace.embargo.DefaultEmbargoLifter


(For submitting through the web interface I’ve enabled the submission step to 
let users add an embargo at the bitstream level; I’ve left out the step to add 
an embargo at the item level because this doesn’t suit our workflow. I don’t 
*think* this is relevant here but it might be...)

When I submit an item via Elements, the term “6 months” is put into the field 
lu.embargo.ends (I’ve verified this by checking directly in the database).
When I check the metadata when it’s in workflow, I don’t see any end-date 
calculated – so I assume that it’ll calculate this on committal to the archive.
But when I click ‘commit to archive’ I get the error: “Embargo lift date must 
be in the future, but this is in the past: 6”

So it appears to be attempting to interpret the term “6 months” as a date by 
throwing out the alpha characters and complaining that 6 < 2016-11-04  - 
instead of converting “6 months” -> 182 days and adding that to the current 
date as I thought it was meant to do.

Am I missing something; or is this a bug; or is it a bad interaction with 
Elements?


Kā mihi maioha,

Deborah Fitchett
Senior Advisor, Digital Access
Library, Teaching and Learning

p +64 3 423 0358
e deborah.fitch...@lincoln.ac.nz | w 
ltl.lincoln.ac.nz

Lincoln University, Te Whare Wānaka o Aoraki
New Zealand's specialist land-based university



P Please consider the environment before you print this email.
"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."

-- 
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] embargo and request a copy doubt

[Victoria Parra]

good day guys. how are you?. I am writing  you today because I have a doubt 
with embargo and request a copy function.
I have dspce 5.4 with jspui and I enabled simple embargo. it work fine but 
I have a doubt. when I enable simple embargo I can use request a copy 
function. because I put a item with embargo but with other user diffenent 
to administrator user I see item but when I do click to item this give a 
message that say that these user haven't authorization to see it item. and 
I can see nothing more. I can't see green button request a copy.
 ¿ I need configure something about authorization with administrator 
account?. maybe give some privilege or I need configura some file?.
 thank you for your help guys!

and excuse me for my bad english!

-- 
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] embargo and request a copy doubt

[Victoria Parra]

good day guys. how are you?. I am writing  you today because I have a doubt 
with embargo and request a copy function.
I have dspce 5.4 with jspui and I enabled simple embargo. it work fine but 
I have a doubt. when I enable simple embargo I can use request a copy 
function. because I put a item with embargo but with other user diffenent 
to administrator user I see item but when I do click to item this give a 
message that say that these user haven't authorization to see it item. and 
I can see nothing more. I can se green button request a copy.
 ¿ I need configure something about authorization with administrator 
account?. maybe give some privilege or I need configura some file?.
 thank you for your help guys!

and excuse me for my bad english!

-- 
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] Embargo and metadata dc.rights.accesRights in DSpace 5.5

[Franziska Ackermann]

Hi,

If the information is just needed for OpenAIRE, could you use the 
crosswalk to fetch it dynamically ?


I have seen this for various information on bitstreams in ore.xsl and 
mets.xsl, e.g. format, URL, size, checksum, ...
Could this be done for the access condition as well or is it stored 
differently ?


Best regards,
Franziska//Ackermann/
/


Am 09.06.2016 um 10:47 schrieb emilio lorenzo:


Hola Mariaangels

The best way is to program a curation task that reviews 
file-permisions, and suggest (or do) such change when that condition 
is detected.


Best luck

Emilio




El 09/06/2016 a las 10:27, Mariangels escribió:

Hola,

I'm working with DSPace 5.5 and xmlui Mirage theme.

In our repository we need always to fill the metadata:

/*dc.rights.accesRights*/

with this value:

/info:eu-repo/semantics/embargoedAccess/

when an item is embargoed.

When the embargoed is finished//I need to change this value and put:

/info:eu-repo/semantics/openAccess

/can DSpace 5.5 do this automatically when an embargo is finished?

Thanks in advance.










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


--
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] Embargo and metadata dc.rights.accesRights in DSpace 5.5

[emilio lorenzo]

Hola Mariaangels

The best way is to program a curation task that reviews file-permisions, 
and suggest (or do) such change when that condition is detected.


Best luck

Emilio




El 09/06/2016 a las 10:27, Mariangels escribió:

Hola,

I'm working with DSPace 5.5 and xmlui Mirage theme.

In our repository we need always to fill the metadata:

/*dc.rights.accesRights*/

with this value:

/info:eu-repo/semantics/embargoedAccess/

when an item is embargoed.

When the embargoed is finished//I need to change this value and put:

/info:eu-repo/semantics/openAccess

/can DSpace 5.5 do this automatically when an embargo is finished?

Thanks in advance.










--
You received this message because you are subscribed to the Google 
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to dspace-tech+unsubscr...@googlegroups.com 
.
To post to this group, send email to dspace-tech@googlegroups.com 
.

Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "DSpace 
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Embargo and metadata dc.rights.accesRights in DSpace 5.5

[Mariangels]

Hola,

I'm working with DSPace 5.5 and xmlui Mirage theme.

In our repository we need always to fill the metadata: 

*dc.rights.accesRights*

with this value:

*info:eu-repo/semantics/embargoedAccess*

when an item is embargoed.

When the embargoed is finished I need to change this value and put:



*info:eu-repo/semantics/openAccess*can DSpace 5.5 do this automatically 
when an embargo is finished?

Thanks in advance.







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