researcher dashboard - untitled entries...possibility of purging or categorising differently

15 views
Skip to first unread message

Christopher McAvaney

unread,
May 19, 2014, 8:41:34 PM5/19/14
to redbo...@googlegroups.com
Just wondering if purging old "untitled" entries within plans or datasets has been considered before?
Would it be possible to purge these untitled entries if they haven't been touched for a configured period of time (e.g. a month).

Or would it be possible to group them in the researcher dashboard so that they can be filtered from view?
It makes the dashboard cluttered, especially as an administrator of the list.

Thoughts?

Regards,
Christopher

Sharyn Wise

unread,
May 19, 2014, 10:58:41 PM5/19/14
to redbo...@googlegroups.com
Hi Christopher 

I agree that its a nuisance. Perhaps it would be better if  Redbox cleaned up after itself by deleting empty structures that aren't explicitly saved? 

kind regards
Sharyn


--
You received this message because you are subscribed to the Google Groups "ReDBox Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redbox-dev+...@googlegroups.com.
To post to this group, send email to redbo...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/redbox-dev/37a1f7de-68d3-4a60-83ce-85cba793b6a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Christopher McAvaney

unread,
May 20, 2014, 12:47:38 AM5/20/14
to redbo...@googlegroups.com

Yeah – that could work.

 

Duncan – would this be easy to do?

 

Regards,

Christopher

 

Dr Christopher McAvaney

Director eResearch

Deakin eSolutions and Deakin Research

Deakin University Victoria Australia.

postal: Geelong Waurn Ponds Campus, Locked Bag 20000, Geelong, VIC 3220

physical: 75 Pigdons Road, Waurn Ponds, VIC 3216
p: +61 3 5227 2676

m: +61 4 3930 0266

e: christophe...@deakin.edu.au

w: http://www.deakin.edu.au/research/
Deakin University CRICOS Provider Code 00113B

 

treePlease consider the environment before printing this email.


For more options, visit https://groups.google.com/d/optout.


Important Notice:
The contents of this email are intended solely for the named addressee and are confidential; any unauthorised use, reproduction or storage of the contents is expressly prohibited. If you have received this email in error, please delete it and any attachments immediately and advise the sender by return email or telephone.

Deakin University does not warrant that this email and any attachments are error or virus free.

Andrew Brazzatti

unread,
May 20, 2014, 1:10:03 AM5/20/14
to ReDBox Developer List
Hi Christopher

It wouldn't be too difficult, you'd construct a housekeeping job that performs a query against solr to determine the records that have been created and never updated with the title"[Untitled]" and then use that result set to delete the records out of storage and the index. As it's a housekeeping job, you could then set it up to run periodically.

Thanks,
Andrew


Christopher McAvaney

unread,
May 20, 2014, 1:28:45 AM5/20/14
to redbo...@googlegroups.com

Is there a “cheat sheet” how-to doco on coding housekeeping jobs?

 

Regards,

Christopher

 

Dr Christopher McAvaney

Director eResearch

Deakin eSolutions and Deakin Research

Deakin University Victoria Australia.

postal: Geelong Waurn Ponds Campus, Locked Bag 20000, Geelong, VIC 3220

physical: 75 Pigdons Road, Waurn Ponds, VIC 3216
p: +61 3 5227 2676

m: +61 4 3930 0266

e: christophe...@deakin.edu.au

w: http://www.deakin.edu.au/research/
Deakin University CRICOS Provider Code 00113B

 

treePlease consider the environment before printing this email.

 


For more options, visit https://groups.google.com/d/optout.

Andrew Brazzatti

unread,
May 21, 2014, 1:18:19 AM5/21/14
to ReDBox Developer List
Hi all,

It turned out to be a little more complicated than I anticipated due to some quirks of the Fascinator platform, so I've committed a version of the housekeeping job to the core of ReDBox.
The commit details can be found here

If you would like to use this before the next release of ReDBox you will need to:
  1. copy both the files in the commit to your institutional build
  2. replace all instances of date_object_created with create_timestamp in the purgeEmptyRecords.py. Reason for this is that this property is a new one property only available in the next release but for the purpose of this task, create_timestamp should work fine.
In terms of configuring this housekeeping job, you can follow the instructions in the http://www.redboxresearchdata.com.au/documentation/system-administration/administering-redbox/configuring-alerts#TOC-Scheduling-alerts replacing the newalerts.script in the url with purgeEmptyRecords.script

If you only want to restrict it's effect to a specific package type, (e.g. dataset) you can also provide the parameter packageType on the URL.
e.g. <redbox url>/default/hkjobs/purgeEmptyRecords.script?packageType=dataset

Now for some warnings :)
  1. Please test this on a non-production environment before using it in production. This script physically purges the record out of storage and the solr index without a trace (except for a log entry saying that it has been deleted) so if it greedily picks up records that it shouldn't for deletion the result could be catastrophic.
  2. Along the same lines, ensure you are backing up ReDBox at least as often if not more often than this script runs so that you can recover from should anything bad happen.
  3. This script relies on the eventLog index (our audit log) to determine whether any edits have occurred on this record. If you've ever moved ReDBox to a new host (or installation) and have missed moving the eventLog index, then it's not a good idea to use this script.
Feel free to modify and contribute improvements to the scripts, it uses the standard portal view code. Documentation on how it all works can be found here

Thanks,
Andrew


Christopher McAvaney

unread,
May 21, 2014, 2:10:01 AM5/21/14
to redbo...@googlegroups.com
This looks good, will include evaluation of this in our upgrade project when v1.7 is available.

Regards,
Christopher
Reply all
Reply to author
Forward
0 new messages