forked from FieldDB/FieldDB
-
Notifications
You must be signed in to change notification settings - Fork 0
Home
cesine edited this page May 16, 2012
·
36 revisions
Welcome to the FieldLinguistics Database Project!
Our basic requirements:
- non proprietary
- OpenSource
- Offline
- HTML5
- Unicode
- OpenData enabled
- Simple
- Collaborative
- make your own categories
- Tags/keywords (e.g. antipassive)
- Designed for search
- Runs on touch tablets (Android, iPad)
- Drag and drop audio to attach audio to your data
- IPA
- Smart
- Import .csv
- Import ELAN
- Similar Software for Fieldlinguistics
- Similar Software for sharing data
- Software which can be used for the Auto Glosser Module
We have some small funding TBA
- Alan Bale (McGill, Concordia)
- M.E. Cathcart (iLanguage Lab)
- Gina Cook (iLanguage Lab)
- Jessica Coon (McGill)
- Theresa Deering (iLanguage Lab)
- Yuliya Manyakina (Concordia)
- Hisako Noguchi (Concordia)
- Robert Henderson (UC Santa Cruz)
This project is released under the (Apache 2.0)[http://www.apache.org/licenses/LICENSE-2.0.html] license, which is an very non-restrictive open source license which basically says you can adapt the software to any use you see fit.
- simple (cute design)
- friendly (the software needs to be localizable, it will start in English, French and Spanish since we will be launching it in Guatemala)
- collaborative (need teams and users)
- make your own lines (have a design page so they can set their lines and add new ones, and change the order, and decide which lines are rare)
- tags (have tags and be able to use the tags for search, mostly for "constructions" like "passives" or other things that may or may not really exist but have been used in the literature.)
- search (progressive search, intersect and union search)
- unicode (all the pages are unicode, technically all the input data will be unicode automatically. needs testing..)
- offline (use local storage in the chrome extension, sync when the user clicks sync, in later iterations, try to sync in other ways)
- anywhere (need teams and users, and a central server to server the various browsers, chrome is supported, but others like Opera and Safari will work)
- ipa (we really need ipa support, but the ipa keyboard is tricky, this needs looking into)
- smart (we will set up the logic for the software to guess morphological parsing, and glosses, this should be a plugin so that the "smart" can be from anyone's existing morphological parser)
- import .csv (it will be super userful to import csv data sets while testing and developing so that we dont have to enter data manually to test the system)