!!!Planning meeting, risten.no Agenda # Opening # Status quo and open issues # Tasks ahead ## risten.no ## Divvun ## kvensk # Actions # Timetable !! Opening Started 11.05 Participants: Risten, Sjur, Tomi Inga Margrethe is not taking part. !! Status quo and open issues SD is organised in teams, Risten is managing "Terminologi- og stedsnavnsteam". Hasn't had so much time for risten.no yet. Pia, Elle-Kirsti and xxx has received training in using risten.no. Improvements to increase the speed of registration: * add whole lists * concurrent editing * multiple parallel term collections and general dictionaries There's a big need for corrections in risten.no - a lot to do! !! Tasks ahead ! risten.no * multiple parallel term collections ** e.g. the Mekanikerliste by Svein Lund & co * multiple general dictionaries * multiple users, with restricted and concurrent access * import whole lists into risten.no as separate collections ** define the xml format ** conversion routines ** metadata required * rework the classification system * improvements to the editing: ** it should be possible to add a new record when nothing is found in a search *** No hits! -> Button to add new entry ** upon saving, the returned receipt should be replaced with the full article entry, for further elaboration ** get a list of search terms that are ''not'' found *** can be extracted from the logs ! Divvun The Divvun project is considering risten.no as storage and editor for the proper names. ! kvensk There is a kvensk revitalization project, that would like to use our tools. It includes a kvensk place name project. !! Actions Immediate actions: * fix the multiuser bug (__Sjur__) * prepare for multiple collections (__Tomi__) Suggestions * merge existing place names in risten.no with the proper name lexicon from Divvun, as well as with place names from the kvensk project, and probably also from the map authorities. * define a standard xml format for new lists * make a tool to convert incoming word lists to this format * define required metadata !! Timetable * multiuser bug: 2-3 weeks * multiple collections: 2-3 weeks * roughly in the same timeframe