Linguista
commented
7 years ago Regarding point 3, "opening the existing sound file within a sound file editor on the user's computer, mostly PRAAT", note that Praat doesn't directly modify sound files; the process is rather more convoluted: it imports a sound file as an object, modifies the object (but not the file on the disk), and then if you choose to you can save the new object as a new file. You should not normally be able to save the new file over the old one, due to OS file locking.
In practical terms, this means the new site functionality should be able to deal with exporting a file with one name, importing the edited file with another name, and then changing the name of the edited file to the original name. (Users could also save the new file with the original name in a new directory, but that could get confusing).
PaulHeggarty
This is a very big new functionality to be added to the Sound Comparisons system.
There should be two types of 'Editor Mode': 1)
Data Editor Mode(this issue #425, the feedback parallel toData Feedback Mode, #427 ) 2)Translation Editor Mode(issue #426, the feedback parallel toTranslation Feedback Mode, #428 )This
Database Editor Modewill take a few weeks of programming, perhaps, but will totally transform the efficiency of quality control and data correction right across Sound Comparisons.[ ] There should be a new log-in icon in the header bar, top right, where admin users can log in.
[ ] Once logged in, another icon should be visible, a toggle which when clicked switches to database editor mode.
[ ] Once in database editor mode, a mini 'edit' icon should appear in each cell that contains a sound file and/or transcription, on any of the table views, and in the bubbles on the map. (Or some other appropriate way to trigger editing an entry, such as double clicking.)
[ ] Database editor mode should allow, in any 'sound file/transcription' cell: 1) Altering a phonetic transcription directly, and when saved it replaces the corresponding transcription in the database. 2) Replacing a sound file by allowing upload of a new one, automatically renamed to the right name corresponding to that cell. 3) If possible, opening the existing sound file within a sound file editor on the user's computer, mostly PRAAT, I presume. Editing it, and then saving it from PRAAT back to immediate upload as in 2). 4) Editing any other data in that cell, such as cognate set or loanword indicators (not yet currently working well anyway).
[ ] This editor mode also needs to work in the offline version of the site, in fieldwork contexts. This means that all changes will then have to be uploaded together, to synchronise the online version to the changes made offline.
[ ] In fact, the log-in should be part of a new log-in and rights system, preferably combined with CoBL log-in, and even using some external log-in system, perhaps like github's. All to be discussed, and a separate issue set up for this in due course.