From: Matt Price <moptop99@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Showing Property in headline; generating table from properties; exporting table to CSV
Date: Thu, 6 Aug 2015 12:39:23 -0400 [thread overview]
Message-ID: <CAN_Dec9_uWa=WQeRdEAS-vnym+Oq-T3fruh-Ytu-cCRRAkU4Og@mail.gmail.com> (raw)
In-Reply-To: <m2k2t8h539.fsf@andrew.cmu.edu>
[-- Attachment #1: Type: text/plain, Size: 3718 bytes --]
I'm reading through gb-grade and grade.el, I see you do something
interesting with rubrics, could you provide a link to a syllabus document
with example rubrics?
On Thu, Aug 6, 2015 at 10:19 AM, John Kitchin <jkitchin@andrew.cmu.edu>
wrote:
> All my gradebook related stuff is here:
> https://github.com/jkitchin/jmax/tree/master/techela, and there is a lot
> of it ;)
>
> I have a whole ecosystem built around using git through emacs and
> org-mode with my students, which at this point even I find complex!
>
> For grading, I grade directly in the student's turned in org-file using
> functions from here
> https://github.com/jkitchin/jmax/blob/master/techela/techela-grade.el. I
> define a minor-mode with a keymap to make grade entry, commenting,
> etc... relatively easy for me. The grades are weighted by different
> categories, and saved as a filetag (not a property). I tend to put one
> problem per file so the grade is just for the one problem, and assign
> 2-3 of these per week.
>
> For gradebook stuff, most of it is here:
> https://github.com/jkitchin/jmax/blob/master/techela/techela-gradebook.el
>
> The grades are stored in the student org-files which I return to them. I
> lookup all the assignments from the syllabus, and then map over the
> org-files for each student for each assignment getting the grades out.
>
> I will be using it again this fall, so /maybe/ the documentation will
> even improve ;)
>
> Matt Price writes:
>
> > On Thu, Aug 6, 2015 at 9:13 AM, John Kitchin <jkitchin@andrew.cmu.edu>
> > wrote:
> >
> >> How do you enter your grade? I use a function, bound to a convenient key
> >> like s-s g, which sets the grade property. You could have that function
> >> change the heading TODO state to DONE so you know it is done, and maybe
> >> add a tag with the grade, or just append the grade on the end of the
> >> headline.
> >>
> >
> > I just set the grade with "C- C-x p GRADE", too slow! I would love to
> see
> > your function though I can doubtless at least write THAT myself. Yeas,
> then
> > having that same function change the todo state (to "READY" in my case
> -- I
> > change to "DONE when I email out the comments), would make a lot of
> sense.
> >
> > Adding the grade as a tag doesn't seem quite right, as I often change
> > grades after a rewrite. I'd need to get rid of the original tag. Adding
> > to the headline might work, but I'd have to change some of my existing
> > functions which use the headline value as a proxy for the student name.
> > Could definitely be done.
>
> see previous email about using overlays
>
> >
> >>
> >> I also use a function that runs org-map-entries and constructs a
> >> temporary gradebook as an org-table in a new buffer.
> >>
> >
> > please please show us? Thank you!
> >
> >
> >
> >>
> >> Eric S Fraga writes:
> >>
> >> > On Thursday, 6 Aug 2015 at 07:24, Matt Price wrote:
> >> >
> >> > [...]
> >> >
> >> >> - I currently store my grades as properties of level-2 headlines.
> >> However,
> >> >> I would really like to be able to see the grades when the headline is
> >> >> folded, so I can have a quick visual sense of how many papers I've
> >> marked,
> >> >
> >> > I would like something like this as well. The nearest I have found is
> >> > to use column view.
> >>
> >> --
> >> Professor John Kitchin
> >> Doherty Hall A207F
> >> Department of Chemical Engineering
> >> Carnegie Mellon University
> >> Pittsburgh, PA 15213
> >> 412-268-7803
> >> @johnkitchin
> >> http://kitchingroup.cheme.cmu.edu
> >>
>
> --
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>
[-- Attachment #2: Type: text/html, Size: 5406 bytes --]
next prev parent reply other threads:[~2015-08-06 16:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 11:24 Showing Property in headline; generating table from properties; exporting table to CSV Matt Price
2015-08-06 11:28 ` Eric S Fraga
2015-08-06 11:34 ` Nicolas Goaziou
2015-08-06 12:17 ` Eric S Fraga
2015-08-06 12:24 ` Matt Price
2015-08-06 13:44 ` Nicolas Goaziou
2015-08-06 13:13 ` John Kitchin
2015-08-06 13:29 ` Matt Price
2015-08-06 14:19 ` John Kitchin
2015-08-06 16:39 ` Matt Price [this message]
2015-08-06 16:47 ` John Kitchin
2015-08-07 16:41 ` Pip Cet
2015-08-10 14:41 ` Eric S Fraga
2015-08-07 1:43 ` Richard Lawrence
2015-08-06 14:06 ` John Kitchin
2015-08-06 16:26 ` Matt Price
2015-08-06 13:52 ` John Kitchin
2015-08-06 17:27 ` Matt Price
2015-08-06 18:14 ` John Kitchin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN_Dec9_uWa=WQeRdEAS-vnym+Oq-T3fruh-Ytu-cCRRAkU4Og@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).