1.8 - 'alert' changes.

8 views
Skip to first unread message

Timothy O'Connor

unread,
Apr 18, 2016, 11:28:58 PM4/18/16
to ReDBox
I am trying to get out 1.8 system up and running - all good really, but I have noticed that by default the alert system is not working.  Records are being put in the system, but are not visible via the UI.

in 'alert.json'

"new-alerts": {
        "alertSet": [
            {
                "name": "Data plans",
                "path": "${fascinator.home}/test-alerts/dataplan1",
                "harvestConfig": "${fascinator.home}/harvest/workflows/dmpt.json",

....

"baseline": {
                    "viewId": "dashboard",
                    "packageType": "dmpt",
                    "redbox:formVersion": "1.6.1-SNAPSHOT",
                    "redbox:newForm": true,
                    "redbox:submissionProcess.redbox:submitted": true,
                    "workflow_source": "Default Alert"
                }

This appears to be the problem.  Changing it to:

"new-alerts": {
                "alertSet": [{
                        "name": "Data plans",
                        "path": "${fascinator.home}/test-alerts/dataplan1",
                        "harvestConfig": "${fascinator.home}/harvest/workflows/dataset.json",
....

"baseline": {
                                "viewId": "default",
                                "packageType": "dataset",
                                "redbox:formVersion": "1.8",
                                "redbox:newForm": "true",
                                "redbox:submissionProcess.redbox:submitted": "true",
                                "workflow_source": "Default Alert"
                        }

works.

Can someone explain what the difference between dmpt and dataset is?  if I should be using dmpt, what settings do I need to make to make the alert 'incoming' record visible?

Matthias Liffers

unread,
Apr 19, 2016, 8:19:29 PM4/19/16
to redbo...@googlegroups.com

Hi Timothy,

 

We’ve been using the alerts system quite a bit to import records from a LIMS.

 

In this case, “DMPT” stands for “Data Management Planning Tool”, which is a piece of ReDBox functionality we’re not using at all. I believe the point was for researchers to use the data management planning tool to send alerts to librarians that there is a new dataset to publish. A librarian then needs to take that data management plan and convert it to (or create) a dataset record. There is a particular view that you need to use in ReDBox to access the data management plans. As I said, we’re not using it, so I can’t give you more detail than that.

 

Your working configuration is similar to ours. We harvest a CSV and use that to create a dataset record right away, skipping the unnecessary data management plan.

 

    "new-alerts": {

        "alertSet": [

            {

                "name": "TIMADataset",

                "path": "${fascinator.home}/lims-alerts/tima/dataset",

                "harvestConfig": "${fascinator.home}/harvest/workflows/dataset.json",

                "baseline": {

                    "viewId": "default",

                    "packageType": "dataset",

                    "redbox:formVersion": "1.6.2-SNAPSHOT",

                    "redbox:newForm": "true",

                    "redbox:submissionProcess.redbox:submitted": "true",

                    "workflow_source": "JDLC TIMA",

                }

 

The baseline section is quite powerful. We’re importing dozens of records where the vast majority of fields are identical (similar mineral analyses on the same instrument), so they are all hardcoded in baseline. The CSV that contains the metadata that varies from analysis to analysis can be stripped back and quite lean.

 

“name” and “workflow_source” can be set to whatever you want. The contents of “workflow_source” will actually appear in ReDBox in the little Alerts box, like this:

 

 

Regards,

 

Matthias Liffers
BCompSc W.Aust. MInfoStud CSturt AALIA (CP)
Coordinator, Research Services | University Library

Curtin University
Tel |
+61 8 9266 2439
Fax | +61 8 9266 4185

Email | matthias...@curtin.edu.au
Web | http://library.curtin.edu.au

ORCID | http://orcid.org/0000-0002-3639-2080


Description: email_logo.png

 

Curtin University is a trademark of Curtin University of Technology.
CRICOS Provider Code 00301J

--
-- Website: http://www.redboxresearchdata.com.au
 
You received this message because you are subscribed to the Google Groups ReDBox group. To post to this group, send email to redbo...@googlegroups.com. To unsubscribe from this group, send email to redbox-repo...@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/redbox-repo?hl=en
---
You received this message because you are subscribed to the Google Groups "ReDBox" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redbox-repo...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Timothy O'Connor

unread,
Apr 25, 2016, 7:51:39 PM4/25/16
to ReDBox
Awesome, thanks Matthias :)  I am assuming that these records still need to go through the normal redbox curation process?  i.e 'Investigation', 'Meta Data Review', 'Final Review', 'Published'?  
Reply all
Reply to author
Forward
0 new messages