You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Different students often make similar mistakes. To this end, I often use raw (as in, human brain) memory, and grep at best, to find a comment that I had previously given, and paste it in for another student. Clearly, both are imprecise. It would be nice to be able to query into remarks files to list just the remarks under a particular judgement and/or structural remark. This would make it easier to recall what sort of comments have been given under a particular point, and to find the comment one is thinking of.
I guess this calls for something like XPath or CSS selectors; just for remarks.
The text was updated successfully, but these errors were encountered:
oleks
changed the title
Query for remarks
Query language for remarks
Mar 9, 2021
Maybe this is best done by allowing the export of remarks data into some other structured format that already has a query language.
I don't think the idea was well-formed at the time. It makes more sense that I open a remarks file, place my cursor under a judgement/remark, and ask my editor to tell me what else I, or some other (re)marksman, has put under that judgement/remark.
I have been toying with the idea of a web-based UI in general, but I guess some editor modes would be more in line with the initially plain-text file format.
Different students often make similar mistakes. To this end, I often use raw (as in, human brain) memory, and
grep
at best, to find a comment that I had previously given, and paste it in for another student. Clearly, both are imprecise. It would be nice to be able to query into remarks files to list just the remarks under a particular judgement and/or structural remark. This would make it easier to recall what sort of comments have been given under a particular point, and to find the comment one is thinking of.I guess this calls for something like XPath or CSS selectors; just for remarks.
The text was updated successfully, but these errors were encountered: