Skip to content

Conversation

@chrisndodge
Copy link
Contributor

...the course structure. This is used by researchers to get metadata to associate with analytics data.

…of the course structure. This is used by researchers to get metadata to associate with analytics data.

remove exception handling, just let it fail
@chrisndodge
Copy link
Contributor Author

@rocha this puts back that django-admin utility that we removed a few months ago. Seems like researchers still need this, so we should get it back to master.

@rocha
Copy link
Contributor

rocha commented Feb 7, 2014

@chrisndodge
We moved it here: lms/djangoapps/courseware/management/commands/dump_course_structure.py

We currently are providing the output of that command (JSON course structure) to the researchers in our weekly dump.

@chrisndodge
Copy link
Contributor Author

Ah, is the output schema the same? I'm still very confused, why course teams still need to get us to generate these?

Is the problem that they have to change their scripts since the output of your JSON is different than what we had delivered before?

@rocha
Copy link
Contributor

rocha commented Feb 7, 2014

The output should be very similar, since it is based on your script. I think there are a few extra fields and that is it.

As a note, we provide data exports to the data czars, not the course teams. The teams may request the data from their corresponding data czars, but only if it is for research purposes. Each university has a different policy about it.

I am not sure why the course teams are requesting the JSON data, nor what they are doing with it. I think that is part of the reason no one has taken care of it so far.

@rocha
Copy link
Contributor

rocha commented Feb 10, 2014

I am closing the pull requests, since this functionality is provided by another command.

@rocha rocha closed this Feb 10, 2014
@benpatterson benpatterson deleted the cdodge/add-dump-course-structure branch January 21, 2015 13:12
jenkins-ks pushed a commit to nttks/edx-platform that referenced this pull request Jun 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants