The Chinesepod long-term wish list...

You ask for a Data model? The following one I did I think in March 07 in a kind of modeling delirium: ;)

Goulniky: thanks for that software suggestion... however I work for a school run by state government which means there are firewalls and restrictions around every corner (for good reason, I'm sure). However, I imagine I could expect to encounter the same problem (inability to simultaneously toggle between exercises while playing the audio clip), if I were using a public computer at a library or internet cafe, right? I've only been a premium subsriber for about a week now, but I can see the benefit of having the mini-audiofile links for vocabulary words carried-over to our "tagged" lists. Hearing a word or phrase repeated on demand would help it sink in auditorally, just like reading it does visually. Henning... the data model is "just a little complex"? I'm stuck trying to decipher whether the model will help guide me through the maze of hutongs in Beijing, or if it will make me some money in the office March Madness (college hoops) pool! In all seriousness, nice job. :u)

for starters, I'd only ask for The Fix to be recorded retroactively on older lessons (whatever the impact on my mp3 storage), measure words to be listed along all nouns in the vocab, and this section to be searchable.

I can hear Ken now: "The following staff meeting is brought to you by Henning!" Many good suggestions, but I especially like both of goulniky's and Henning's about the QW/grammer guide homework. And Henning, in the future, with your permission, instead of giving my students tests, I think I will inform them that I'm offering "Enhanced Progress Tracking Features."

Web services! Faster page response times

-an extra-section with chinesepod fan-articles -a little window at the "home" page where you can enter lesson requests so that you can send ém in right when you have the idea.

Definitely support the dictionary suggestion, and the creation of learning games. How about the ability to play a lesson/dialogue while simultaneously being able to jump between expansion, exercises, and posting comments (for those of us that are prevented from performing downloads on our {ahem} work computers).

mandomikey; performing downloads on {ahem} computers can often be done using {meha} software such as {frusartlu}. You need to work it out in the looking-glass lest it self-destroys in the great firewall though.

I am in complete awe!!! One's wish list is another's present. A Christmas present for poddies and chinesepod.

*** Warning: Some readers might be offended by the following comments. *** 1. As an idea I was thinking of ChineseBot - you're ultimate Chinese learning companion, hooked to the net, adapted to your individual needs and capabilities and always willing to explain the difference between 十 and 四 etc. 2. As a VISION Chinesepod should go for being the ultimate learning method to easily, reliably and individually acquire language competence to confidentially communicate in Chinese and express oneself. 3. Critical comment on Henning's suggestions: I don't see the learner in those diagrams. He or she is obviously supposed to sit in front of the machine. In my view, this is the wrong way to model things. Furthermore, the network perspective is missing, i.e. it's about a community of learners. ;-)

WOW! That's unbelievable! It makes me head spin just looking at it.

Sounds reasonable to me! (And yes, I do remember Memory Isle...)

I am going to post some psychology vocab in relation to the Phobia lesson I just went through with Vera today. I've posted other vocab lists before, ideally this and other user-generated content should be integrated into the knowledge base. Not sure how, point being that all comments are valuable but some of the banter is loosely related to the lesson topic, technical support and general discussion stuff.

I liked Memory Isle too, although I never figured out what the 2 hour animated ending was supposed to mean. On the server speed problem -- we're aware of the issue with response time -- SpanishPod traffic is starting to cramp-up our CRM. I'm hoping to solve this soon by adding extra server capacity in the US. Trying to arrange this as quickly as we can given the fact that we're here and they're there....

why 6000 characters ? where does this number come from (vs 5000, 7000, 8000, etc.) ?

Nicolas, The 6000 characters (well, 6763, if you want to get picky) comes from the number of characters encoded in the GB2312 standard, which is still the most widely used encoding scheme for Chinese. For the most part, if the character doesn't exist it GB2312, its not going to be found in anything modern, so it makes it a good character acquisition goal.

My wish list contains only one item, and I don't want anything else until we get it. What I would like to see is a regular time for technical maintenance each month, something like "9-12am Shanghai time on the first Tuesday of each month". During this maintenance time some or all services could be taken off line for a period of time, if that month's maintenance required it... or if something went wrong as we know it can, although most months we wouldn't even notice work was being done. It's a safety net, for all of us. The advantages would be that - maintenance could be performed incrementally, following the best practice principle of changing only one thing at a time rather than saving them up for a big bang. - there would not be undue pressure on tech staff to schedule around marketing rather than need, so they'd be able to do their best work according to their own best plans - maintenance could be performed in a proud responsible manner, without shouting about a few token enhancements to pretend that they were the real reason. We're all grown up, we know what maintenance is, and that it's gonna be essential and frequent to have a reliable system, and for most of us reliability/predictability is the most critical feature. - we would know when the maintenance is likely to happen, always, and nervous types could work our studies around it "just in case". The majority of the time when there was no visible effect on the system, we'd be pleased, rather than the other way round. It would also prompt us to (optionally) mark our own study calendars for a monthly extract of vocabulary or whatever, and we might even use that memory jogger to do a regular backup of our own home computers (wonders never cease!) - if the site was a little slow, we'd look at the calendar, go oh yeah, and be pleased that work is being done, instead of kicking and screaming about missed study opportunities and lack of communication - there would be no requirement for communication about technical maintenance, no need at all, we wouldn't even want to know about it, whenever it was carried out within that monthly four hour period - it would give better opportunities for all the diverse talents within the organisation to appreciate and support each other's projects and aspirations, whether their areas be academic or the more essential prerequisites like servers and software Then, after that's happened a few times and future planning kicks in, ask me again about a feature wish list. Until then, I don't want any new features, ever! :-)

AuntySue: A fixed schedule for maintenance sounds like a good idea to me if it's an hour once a month only. Unless, of course, it deprives listeners in the CET (CEST) longitudes of their daily new lesson at around local breakfast time. I guess Henning, Bazza and Christian are in support of this request! ;-)

Joachim, to clarify, I wasn't talking about four hours down every month, but rather, a four hour period during which there might be short periods of disruption or degraded performance, or indeed the odd half hour of downtime some months. Even if it was down for four hours one maintenance time (most unlikely), wouldn't that be better than what we've just experienced? If you want to restrict all this to a one hour period, sorry, that's useless, gremlins don't work to a schedule. If that's all you'd accept, we'd have no choice but to go back to the old idea of three weeks of "it should have worked" unanticipated peril twice a year, and not knowing about it in advance. The fact is, there MUST be downtimes and/or degraded performance in order to keep a system this size working at all. Would you rather push it under the carpet and have long unexpected ones which are complex to repair, or rather put up with regular shorter known periods of risk? Fact is, there's no way round it so no use pouting and pretending until the whole thing crashes around our ears. When you hold onto something too tight, you lose it. That seems to be exactly what we're trying to do if we restrict maintenance. Think, what happens if you try to run your car without putting air in the tyres or handing the whole car over for a grease and oil change or new brake linings? It's not negotiable.

Joachim, you are absolutely right. The more I read here and look at it the more stuff I see that is missing (e.g. measure words, further descriptions,...). The learner entity type is integral and should be connected to almost everything including reflexively to itsself. I am becoming slightly afraid the diagram could turn out to be just a little complex... :-o