Seems Frank’s code is picking up some steam:
http://forward.library.wisconsin.edu/moving-forward/?p=498
Bruce
I introduced a number of people to CSL and citeproc-js at the
following event: http://www.ukoln.ac.uk/events/devcsi/reading_lists/
I’m happy to report that one of the teams built a very cool teaching
tool using citeproc.
They provided some formatted references on the page (powered by
citeproc), then then they had some fill in text fields below. The
student had to cut and past different parts of the citation into the
correct box, e.g. the student had to correctly identify the volume
number from the citation, the title, that kind of thing.
If they got it right the page provided direct feedback, and if they
got it wrong the page described what was wrong.
This sounds trivial, but for students just encountering citations it’s
a pretty compelling teaching device.
The entire demo was thrown together in under 24hrs. I’ll see if there
is a public snapshot of the demo, and if so I’ll pass it along.
Some of the people interested were developers from the OpenUniversity,
and I think they are taking a serious look at CSL now.
- Ian
I introduced a number of people to CSL and citeproc-js at the
following event: UKOLN | Events | Reading List Hack Event | July 22 & 23 - 2010 | HomeI’m happy to report that one of the teams built a very cool teaching
tool using citeproc.They provided some formatted references on the page (powered by
citeproc), then then they had some fill in text fields below. The
student had to cut and past different parts of the citation into the
correct box, e.g. the student had to correctly identify the volume
number from the citation, the title, that kind of thing.If they got it right the page provided direct feedback, and if they
got it wrong the page described what was wrong.This sounds trivial, but for students just encountering citations it’s
a pretty compelling teaching device.
No, that’s pretty cool! Thanks for the tip!
Bruce