| *** povbot has joined #schooltool | 18:58 | |
| jfroche | some member folder containing bad things are: {'id': 'akula', 'size': 11} | 18:58 |
|---|---|---|
| jfroche | {'id': 'clon', 'size': 12} | 18:58 |
| jfroche | {'id': 'karas6', 'size': 12} | 18:58 |
| jfroche | {'id': 'umaxparty', 'size': 13} | 18:58 |
| ignas | th1a: well, theoretically it is correct, practically it is useless ;) at least at the moment, while yes when i will probably build upon it when transfer to the next year will be required for lyceum | 19:00 |
| ignas | just that the whole machinery required for migration of data from one year to another is something i have no idea about at the moment | 19:01 |
| th1a | OK. I just don't want you to completely disregard it, which your comment implied. | 19:01 |
| th1a | ignas: It is a subject stephan and I worked on at great length... | 19:01 |
| ignas | but i have no access to any decisions, or polished ideas of how should everything work from users perspective ... | 19:02 |
| mgedmin | jfroche: your new ssh key is in place | 19:03 |
| th1a | We mostly worked on modeling things. | 19:03 |
| ignas | modeling things? | 19:03 |
| jfroche | thanks a lot | 19:03 |
| th1a | I mean, designing and implementing the API. | 19:03 |
| th1a | Not so much end-user perspective. | 19:03 |
| ignas | any place where i can find implementations of the API ? | 19:04 |
| th1a | My point is that we need to keep the lines of communication open around that stuff, levels, end-of-year, hierarchical terms, etc. | 19:05 |
| th1a | Yes... | 19:05 |
| th1a | branch: srichter-term-gradebook-work2 | 19:06 |
| th1a | That has the big term rewrite, which is pretty much done. | 19:06 |
| th1a | But the gradebook rewrite never really happened. | 19:07 |
| ignas | it includes the machinery to go from one year to another one ? | 19:07 |
| th1a | I don't think it has that. We never really finalized those pieces. | 19:07 |
| th1a | But it does define a school year and the constituent semesters and grading periods. | 19:07 |
| th1a | Which is obviously a necessary preliminary step. | 19:07 |
| th1a | And also a big pain to do when your current implementation only has flat terms and no year. | 19:08 |
| ignas | well, the simplest implementation (a.k.a. a big RED switch named "Archive data") would kind of work without it ... | 19:09 |
| ignas | what i am interested in is not an API, but a source target comparison, i mean what happens after clicking some magical switch | 19:09 |
| ignas | what data, goes where, and how do you access it, after it is archived etc. | 19:10 |
| th1a | Yes, but you want to be able to analyze data year to year, etc. The system has to understand the passage of time and progress through the school. | 19:10 |
| ignas | not really, it has to understand that the red switch was clicked on 2007-09-01, 2006-09-01, 2005-09-01 | 19:10 |
| th1a | It doesn't seem like anything really needs to be archived as such, or if so, that's an optimization issue. | 19:10 |
| ignas | well, if nothing gets archived, then what happens ? where do students that have graduated go? | 19:11 |
| ignas | i am seeing these things as the difficult probably school specific problem ... | 19:12 |
| th1a | They don't necessarily have to go anywhere. I mean, you'll want to filter them out of most views. | 19:12 |
| ignas | so, we will need some sane way to make all views filter out "archived (not sure it's the right term)" data | 19:12 |
| ignas | and some views that can access it | 19:13 |
| th1a | Yes. | 19:13 |
| ignas | and some ways to mark maybe even hierarchies of objects as archived | 19:13 |
| th1a | You ultimately want to be able to do some long term data analysis which looks at trends over several years. | 19:13 |
| ignas | *mark objects | 19:13 |
| ignas | so the most simple way is to make a huge wizard that guides you through questions like "select groups that should not get archived", "pick students that should not pass to other level", etc. and annotates objects with a flag "archived on school-year 2007" | 19:15 |
| ignas | plus a system that filters everything by these annotations ... | 19:15 |
| th1a | Basically. | 19:16 |
| ignas | what I wanted to say is that it's not really necessary to extend any parts of schooltool functionality to do from users perspective really | 19:16 |
| th1a | There are lots of other things that have to happen at the end of a semester or year, though, you stop taking attendance, generate report cards, possibly activate new sections, etc. | 19:17 |
| ignas | yes, but the migration from one year to another is more of a helper, i mean - levels should help users to transfer people from one kind of groups to another one (in Lithuania), and probably even filter courses by the level of a student | 19:19 |
| ignas | the big red button helps the customer to remove/hide those who are graduated | 19:20 |
| ignas | so he would not have to do it manually | 19:20 |
| th1a | Sure. That would be the default. | 19:20 |
| ignas | one should be capable to simulate the switch between one school year and another by performing a lot of manual tasks | 19:21 |
| ignas | delete these users (maybe add them to a group graduates and disable their passwords) | 19:21 |
| ignas | reset group members | 19:21 |
| ignas | import newbies | 19:21 |
| ignas | create passwords | 19:21 |
| ignas | remove old sections | 19:21 |
| ignas | add new sections | 19:21 |
| ignas | etc | 19:22 |
| th1a | Yes. | 19:23 |
| th1a | Ultimately, we want the labor-intensive parts to be automated. | 19:25 |
| th1a | otoh, we don't want to get so hung up on making a perfect, super-cool automated system that we never ship ;-) | 19:27 |
| ignas | the questions i don't know exact answers for are - what should i do with the data that would get removed if we'd perform a manual migration (need a better term for this :( ) | 19:28 |
| th1a | We really don't want to remove data. | 19:30 |
| ignas | indeed | 19:30 |
| th1a | The actually interesting part of writing a system like this is to do longer term in depth analysis. | 19:30 |
| ignas | well, as soon as some school will last more than a year with schooltool :) | 19:34 |
| th1a | Indeed. | 19:35 |
| jfroche | th1a: this http://www.schooltool.org/portal_skins/custom/checkUsers should help you to find the good users and remove the bad ones | 19:39 |
| th1a | jfroche: It is nice to have a plone expert around. | 19:41 |
| jfroche | "expert" | 19:41 |
| jfroche | have to leave | 19:41 |
| jfroche | good evening | 19:41 |
| *** jfroche has quit IRC | 19:41 | |
| th1a | ignas: anything else before I go to lunch? | 19:43 |
| ignas | you asked what i meant with the Table choice | 19:44 |
| ignas | well - you should have seen the multi column table in person view | 19:44 |
| ignas | and the list of persons you get when you are adding member to a group | 19:44 |
| ignas | i think it would be nicer to have the table with name, last_name, birth_year, maybe groups instead of title | 19:45 |
| ignas | th1a: that's all i think :) | 19:45 |
| th1a | OK. Have a good weekend! | 19:46 |
| *** lex__ has quit IRC | 19:54 | |
| *** alga has joined #SchoolTool | 19:57 | |
| ignas | bye | 20:00 |
| *** lex__ has joined #schooltool | 20:09 | |
| *** lex__ is now known as eukreign | 20:09 | |
| *** eukreign has quit IRC | 20:25 | |
| *** eukreign has joined #schooltool | 20:25 | |
| *** povbot has joined #schooltool | 20:33 | |
| *** eukreign has quit IRC | 20:41 | |
| *** eukreign has joined #schooltool | 20:43 | |
| mgedmin | public service announcements: commit announcements have been discontinued, because the supybot 0.83.2 Debian package helpfully removed the Tail plugin | 20:44 |
| mgedmin | I don't have the time to go look for it | 20:44 |
| mgedmin | the helpful people in #supybot told me I can find it in some darcs repository somewhere | 20:45 |
| mgedmin | that may or may not be called "supybot-plugins" | 20:45 |
| mgedmin | but it is not here: http://supybot.com/supybot-plugins | 20:45 |
| *** eukreign has quit IRC | 20:50 | |
| *** eukreign has joined #schooltool | 20:50 | |
| *** povbot has joined #schooltool | 20:58 | |
| *** ignas has quit IRC | 21:19 | |
| *** faassen has quit IRC | 21:47 | |
| *** jinty has quit IRC | 22:29 | |
| *** Aiste has quit IRC | 23:01 | |
| *** mgedmin has quit IRC | 23:08 | |
| *** alga has quit IRC | 23:41 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!