Re: [Dspace-tech] Advanced Embargo: Dark Metadata

2015-04-21 Thread Robbins, Seth David
Hi Tim, 
For us there a couple of reasons, one is that we’re on Dspace 3, where the
default behavior (if I’m remembering correctly from when we upgraded) was
to withdraw items with the private flag in the InstallItem class. In the
future, we’ll likely just use the private flag to indicate a “dark” item.

The second reason for us to customize the embargo system is that our
original system was an in-house embargo module for space 1.5 (I think the
1.6 plugin was somewhat based on ours, I’m talking about Ideals here so,
Tim, you probably remember). We ended up cobbling together aspects of the
1.6 system and the 3.0 embargo system to more closely replicate the
interface we had previously. Essentially, we needed to support a
campus-only option that the simple embargo form didn’t have, but we didn’t
want to retrain our users to use the Advanced embargo form. We also wanted
to expand our embargo system to allow different embargoes to apply to
individual bitstreams, so we opted not to just port our 1.5 system. Most
of the logic is therefore controlled by resource policies on bitstreams,
but since we’re still supporting high-level item-centric options, we
needed to store that information in the metadata.

Thanks,
Seth   

  
On 4/21/15, 11:01 AM, Tim Donohue tdono...@duraspace.org wrote:

Hi helix84  Seth,

Just out of curiousity, is there a particular reason why you wouldn't
just use the Access Step instead of hacking the same thing via a
temporary withdrawal  reinstate? The Access step already lets you
specify that READ access wouldn't start until a particular date has
passed. But, maybe I'm missing something about your particular use case?

https://wiki.duraspace.org/display/DSDOC5x/Embargo#Embargo-AccessStep

As noted in my other response to this thread, this functionality seems
to already exist as part of the optional Access step (unless I'm
misunderstanding something here?)

http://dspace.2283337.n4.nabble.com/Advanced-Embargo-Dark-Metadata-tp46774
98p4677503.html

- Tim

On 4/21/2015 10:55 AM, helix84 wrote:
 On Tue, Apr 21, 2015 at 5:45 PM, Robbins, Seth David
 srobb...@illinois.edu mailto:srobb...@illinois.edu wrote:

 We do what Helix describes, but we¹re looking for another way. It's
 a hack
 to store information crucial to actionable business logic in the
 descriptive metadata.


 Depends on how you look at it - it is also a way to allow a wider group
 of users to easily edit the date - the 1.6 embargo does the same thing.

 But if you insist, it's not any harder to make the curation task look at
 resource policies instead of item metadata. You could use item resource
 policy or a resource policy of one of the bitstreams or one with a
 special name. Such implementation will still be contained within the
 curation task and doesn't require changes to DSpace.


 Regards,
 ~~helix84

 Compulsory reading: DSpace Mailing List Etiquette
 https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette



 
-
-
 BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
 Develop your own process in accordance with the BPMN 2 standard
 Learn Process modeling best practices with Bonita BPM through live
exercises
 http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
event?utm_
 source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF



 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech
 List Etiquette: 
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Advanced Embargo: Dark Metadata

2015-04-21 Thread Tim Donohue
Hi Peter,

This seems to be exactly what the Access step is for (using either the 
Simple or Advanced settings).

https://wiki.duraspace.org/display/DSDOC5x/Embargo#Embargo-AccessStep

You should be able to just enable that Access Step. Setting the embargo 
via that step applies to the entire Item (including metadata), if I 
recall correctly. By default, if you use the Simple version, it'll 
limit Anonymous READ access (on the Item) so that it starts on the date 
the embargo ends. If you use the Advanced version, you can specify 
exact groups whose READ access should be limited (just be sure to click 
the Confirm Policy  add another for each embargo policy).

I've verified this works properly on the Demo site. Here's an item that 
I just submitted that is fully embargoed until Friday:

http://demo.dspace.org/xmlui/handle/10673/127

By default, when not logged in, it's not visible (you'll see an Item is 
restricted page). But, if you login as the Admin account on the Demo 
server, you'll see it exists.

- Tim



On 4/21/2015 8:32 AM, Peter Dietz wrote:
 Hi All,

 I was wondering if anyone has created a way to modify the embargo system
 to optionally have a way of also setting dark metadata. Meaning, the
 current embargo system will allow the metadata/item to be publicly
 accessible, but the file is restricted until the embargo lift.

 A use case that came up was to have a way to have the embargo also
 restrict the visibility of the item and metadata. Thus, before the
 embargo date, nothing is accessible/visible, and after the embargo lift
 date, the file and metadata will be visible/accessible.

 Thanks
 
 Peter Dietz
 Longsight
 www.longsight.com http://www.longsight.com
 pe...@longsight.com mailto:pe...@longsight.com
 p: 740-599-5005 x809


 --
 BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
 Develop your own process in accordance with the BPMN 2 standard
 Learn Process modeling best practices with Bonita BPM through live exercises
 http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
 source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF



 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech
 List Etiquette: 
 https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


[Dspace-tech] Advanced Embargo: Dark Metadata

2015-04-21 Thread Peter Dietz
Hi All,

I was wondering if anyone has created a way to modify the embargo system to
optionally have a way of also setting dark metadata. Meaning, the current
embargo system will allow the metadata/item to be publicly accessible, but
the file is restricted until the embargo lift.

A use case that came up was to have a way to have the embargo also restrict
the visibility of the item and metadata. Thus, before the embargo date,
nothing is accessible/visible, and after the embargo lift date, the file
and metadata will be visible/accessible.

Thanks

Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809
--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Advanced Embargo: Dark Metadata

2015-04-21 Thread helix84
Hi Peter,

the easiest thing I can think of with no new development is to put the
items in archive as withdrawn, put embargo lift date in a metadata
field and run a curation task daily to to lift the embargo
(reinstate the items).


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


Re: [Dspace-tech] Advanced Embargo: Dark Metadata

2015-04-21 Thread Terry Brady
The only way to accomplish this is to set a policy on the item record with
the same end date as the bitstream policy.  I do not believe that the
submit with embargo  date process can accomplish this.

On Tue, Apr 21, 2015 at 6:32 AM, Peter Dietz pe...@longsight.com wrote:

 Hi All,

 I was wondering if anyone has created a way to modify the embargo system
 to optionally have a way of also setting dark metadata. Meaning, the
 current embargo system will allow the metadata/item to be publicly
 accessible, but the file is restricted until the embargo lift.

 A use case that came up was to have a way to have the embargo also
 restrict the visibility of the item and metadata. Thus, before the embargo
 date, nothing is accessible/visible, and after the embargo lift date, the
 file and metadata will be visible/accessible.

 Thanks
 
 Peter Dietz
 Longsight
 www.longsight.com
 pe...@longsight.com
 p: 740-599-5005 x809


 --
 BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
 Develop your own process in accordance with the BPMN 2 standard
 Learn Process modeling best practices with Bonita BPM through live
 exercises
 http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
 event?utm_
 source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech
 List Etiquette:
 https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette




-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://www.library.georgetown.edu/lit/code
425-298-5498 (Seattle, WA)
--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Advanced Embargo: Dark Metadata

2015-04-21 Thread helix84
On Tue, Apr 21, 2015 at 5:45 PM, Robbins, Seth David srobb...@illinois.edu
wrote:

 We do what Helix describes, but we¹re looking for another way. It's a hack
 to store information crucial to actionable business logic in the
 descriptive metadata.


Depends on how you look at it - it is also a way to allow a wider group of
users to easily edit the date - the 1.6 embargo does the same thing.

But if you insist, it's not any harder to make the curation task look at
resource policies instead of item metadata. You could use item resource
policy or a resource policy of one of the bitstreams or one with a special
name. Such implementation will still be contained within the curation task
and doesn't require changes to DSpace.


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Advanced Embargo: Dark Metadata

2015-04-21 Thread Andrea Schweer
Hi,

On 22/04/15 02:49, Tim Donohue wrote:
 You should be able to just enable that Access Step. Setting the embargo
 via that step applies to the entire Item (including metadata), if I
 recall correctly. By default, if you use the Simple version, it'll
 limit Anonymous READ access (on the Item) so that it starts on the date
 the embargo ends. If you use the Advanced version, you can specify
 exact groups whose READ access should be limited (just be sure to click
 the Confirm Policy  add another for each embargo policy).

This is what we're doing for some of my repositories; however I also 
have a pile of customisations in place (since at least DSpace 1.6.x) to 
make sure the policies are respected everywhere. I don't know whether 
all of these customisations are still needed, perhaps some are overkill. 
I should review these at some point.

With the Discovery rights awareness functionality, you (=the current 
user) will see an item in search/browse etc only when you have READ 
permissions for the item. Viewing the item page is also controlled by 
the item's READ permission; if you don't have that permission then 
you'll get a message / be prompted to log in. So the READ permissions 
definitely cover the basics.

cheers,
Andrea

-- 
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand


--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette