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 YYYY, YYYY-MM, YYYY-MM-DD *and* MM/DD/YYYY 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 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. > -- 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.
