Storing survey data - Githubissues

google-code-export / student-worker-relational-database

Automatically exported from code.google.com/p/student-worker-relational-database

1 stars 1 forks source link

Storing survey data #27

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

Survey data should be importable into SWORD. A form should be built to allow 
supervisor's to view their own student's survey data as long as the student 
still works there. 

Eventually the entire survey could be taken in SWORD.

Original issue reported on code.google.com by dmbs...@gmail.com on 3 Nov 2010 at 8:40

Blocking: #113

GoogleCodeExporter commented 9 years ago

Original comment by dmbs...@gmail.com on 28 Dec 2010 at 4:58

Added labels: Milestone-Release2.0
Removed labels: Milestone-Release1.3

GoogleCodeExporter commented 9 years ago

Issue 65 has been merged into this issue.

Original comment by dmbs...@gmail.com on 25 Jan 2011 at 3:31

GoogleCodeExporter commented 9 years ago

Original comment by dmbs...@gmail.com on 25 Jan 2011 at 3:45

Added labels: Priority-Medium, Milestone-Release1.5
Removed labels: Priority-Low, Milestone-Release2.0

GoogleCodeExporter commented 9 years ago

Original comment by dmbs...@gmail.com on 23 Feb 2011 at 9:55

Added labels: Milestone-Release2.0
Removed labels: Milestone-Release1.5

GoogleCodeExporter commented 9 years ago

Original comment by dmbs...@gmail.com on 11 Apr 2011 at 8:30

GoogleCodeExporter commented 9 years ago

Ok here's the plan for Surveys. I think LimeSurvey will work for us. 

1. Set up LimeSurvey. Brian makes sure it's good. We can do this now. We won't 
have the Google docs problem, if they can access sis.cristoreyny.org they will 
be able to access Lime (survey.cristoreyny.org?)

2. Determine what needs synced in SWORD (both cwsp and alumni data) Brian lets 
talk about the cwsp end soon.

3. Sync that data automatically. My thoughts are that Lime would stay the 
primary location of data and SWORD will access some of this data for various 
uses.

Original comment by dmbs...@gmail.com on 9 May 2011 at 4:10

GoogleCodeExporter commented 9 years ago

Lime up, awaiting feedback.

Original comment by dmbs...@gmail.com on 10 May 2011 at 3:48

Changed state: Started

GoogleCodeExporter commented 9 years ago

Original comment by dmbs...@gmail.com on 20 May 2011 at 5:03

Added labels: Milestone-Release2.1
Removed labels: Milestone-Release2.0

GoogleCodeExporter commented 9 years ago

Original comment by dmbs...@gmail.com on 13 Sep 2011 at 2:04

GoogleCodeExporter commented 9 years ago

Original comment by dmbs...@gmail.com on 13 Sep 2011 at 2:05

Removed labels: Milestone-Release2.1

GoogleCodeExporter commented 9 years ago

This is the oldest outstanding issue :(

We now effectively have a survey making tool from OMR. It probably makes more 
sense to turn that into a online survey tool as well. Just need the time to do 
it.

Also of note LimeSurvey has integration with queXF if we wanted to go that 
route.

Needs some design decisions.

Original comment by dmbs...@gmail.com on 21 Nov 2011 at 5:37