|Self-submission in ReDBox||Duncan Dickinson||9/6/12 5:45 PM|
A number of ReDBox community members have had discussions with me regarding modifications to ReDBox to allow for researcher self-submission and I thought I'd take the opportunity to start looking at how we could achieve this - from a business end rather than a technical end.
Firstly, the model for self-submission is (potentially) based on a model of researcher submissions from a range of workflows, including:
In all of these models, the (ReDBox-biased) workflow might appear as:
So, there are some (many) decisions that need to be made, including:
I don't want to go too far at this point but thought I'd lay a basis for feedback so please send through your thoughts.--
QCIF Project Manager
Central Queensland University
Developer? Check out dev8D-AU at http://dev8dau.info/
|Re: [ReDBox] Self-submission in ReDBox||Peter Sefton||9/6/12 5:56 PM|
I'd add that some of these submission models might actually take place elsewhere, eg Researcher fills out a form in the help-desk system to request storage, and the HelpDesk system or staff deposit part of the form as a DMP. So what I'd suggest for all of these would be to think about a submission API.
-- Website: http://www.redboxresearchdata.com.au
Peter Sefton +61410326955 p...@ptsefton.com http://ptsefton.com
Gmail, Twitter & Skype name: ptsefton
|Re: [ReDBox] Self-submission in ReDBox||Duncan Dickinson||9/6/12 7:47 PM|
Agreed - and this can work through the Alerts system in ReDBox (e.g. http://www.redboxresearchdata.com.au/documentation/how-to/import-rif-cs-into-redbox). In a nutshell, the system can pick up a file (XML but other formats could be made available) and map it into the ReDBox metadata.
|Re: [ReDBox] Self-submission in ReDBox||Peter Sefton||9/6/12 8:03 PM|
Ok, but I think we should be looking at an HTTP based API as well - probably not too hard as it can leverage the forms interface already there - it's all http posts, right?
|Re: Self-submission in ReDBox||meg...@deakin.edu.au||9/10/12 10:03 PM|
Deakin is particularly interested in researcher self-submission. We had noted that ReDBox is very focussed on the administrator. Feedback from our researchers has indicated that expecting them to enter metadata for their collections into ReDBox is likely to deter the researcher from completing a metadata record. It seems very seperate from other activities that they undertake in the research lifecylce therefore is likely to be seen as an additional overhead. We have been considering how we could provide a front end to our researchers that is integrated with their current research practices so that for instance, a metadata record is created automatically when a project is created in ResearchMaster, metadata fields are prefilled with information from ResearchMaster where possible and the record is displayed to the researcher to confirm the information that we already have for their data collection metadata record and provide additional information where they are able to. One of our researchers had suggested that we take a look at academia.edu as an example of a tool that researchers are familiar with using, is focussed and built around the persona of the researcher and that provides questioning functionality (questions them to agree or disagree with publications that may or may not belong to them).
The questions that you pose around the workflow are interesting:
1. It is a very real possibility that the researcher may want to edit the record once it has been submitted for review. Even once the record has been published it may potentially need to be updated. So this is something that will need to be accommodated with researcher self-submission.
2. Not too sure about this one. I think we'd need to ask our researchers if they would want others (who they are able to specify) to be able to edit the metadata record when in the creation stage.
3. We have also been considering how we might implement a data management planning tool to support the researcher to manage their data more effectively. I am interested in your statement about possibly feeding info from the data management plan in to the metadata record. This could be a great way of collecting the required info for the record while also providing valuable input to the data management plan.
4. This idea of linking the collections to the Data Management Plan is one that we would have to investigate further. The researcher may not want to widely share the information in the data management plan but if a link could be made that was only accessible by the creator of the record for instance this may be useful.
If QCIF are seriously considering building a self-submission interface for researchers to submit their own metadata that is focussed on the researcher rather than the administrator, Deakin would be very interested in providing further input to this.
See you at the Virtual infrastructure conference if you're there!
|Re: [ReDBox] Self-submission in ReDBox||Marianne||9/10/12 11:57 PM|
JCU has been doing self submission for a while with our prototype system and are now hoping to move to ReDBox and do the same. We couldn't manage to do everything we wanted in the prototype but here is how we want it to work:
So for Duncan's list of points, JCU's wishlist would be
Project Manager - TDH Project, eResearch Centre
Division of Research and Innovation
James Cook University, Townsville QLD 4811 AUSTRALIA
P (07) 4781 6904; I +61 7 4781 6904; M 0403 889 478
Location: Faculty of Science & Engineering Room 143 (Building 17.143)
JCU CRICOS Provider Code: 00117J