fixed the twitter feed, now appears as two columns
fixes #469 this is a bash script that installs ifield and sets it up for new developers, or for new production servers. it also wraps up and cleans up issues #216 #217 #251 #195 you can look at this script to see how to set up node, how to set up npm, how to set up mongodb and how to clone the github project. this script does all of that for you, this is to make the wiki page https://github.com/iLanguage/iField/wiki/How-to-install-on-your-own-server even easier to use. this script might be useful for #500 #501 #502 #503 screencasts too
fixes #425 @alanbale The prompting sessions are old bug dissapeard about a month ago because i lowered the number of defalt datum in the center data entry area, which was reducing its chance of geting rul to almost 0. Today i fixed it for good (and also got it working so that it will indeed prompt the user only once if the user last modified a datum in the corpus over 24 hours ago, as it was designed to do. (once per time you load the app)
Merge pull request #504 from cesine/master

@mecathcart these are the differences i have
uping the manifest to version 1.19 in preparation for the next release
fixes #508 here is a rough draft of importing elan

also added library so we can read any xml. fixes #506

How the import is working:
it takes each annotation of each tier as a datum, although the elan data is across tiers whcih means this should be re-written to use the elan xml specs and the cross referenceing with in them.

However, rather than perfecting the elan import as xml, we need to know if this is what users want. Do users want to import eaf? If they do, why do they want ot import eaf?

t would be far easier ot import one of ELANs other export formats like tabs, interlinear glosses etc. so we might simply reccomend that users dont import eaf, @balamkej @jessicacoon  this is something we will need input on from someone who actually has their database already in elan. they know elan best...

Our original motivation to use eaf is so that import and export to iField is non-lossy, so that users can use ifield to search, and gloss data, and continue to use ELAN as their primary user interface. What is the probability that real elan users will use ifield. I think it is very low, so this kind of non-lossy import export will take up a lot of development time with no one using it.

What would they use ifield for, if they used it. Would it be for search and glossing? ELAN is opensource and in java, we can write a webservice that does autoglosing for elan users, and they can keep using elan...

Alternatives:
* elan exported as interlinear gloss (see sample_elan.eaf)
* elan exported as praat textgrid (see sample_elan.TextGrid)

I will be using the TextGrid format as the results of the prosody lab aligner, it will be easy for iField to import and export TextGrid. Can TextGrid be our primary format for time aligned transcriptions... how well can elan import and expot textgrids?
putting the annotaiton document details of eaf in to the session and data list details
Merge pull request #510 from cesine/master

Working on more import formats
Update README.md
Merge branch 'master' of https://github.com/OpenSourceFieldlinguistics/iField

changed upstream repo and pulled from it
edited the script for setting up iFied in external server e.g. Mcgill. The script downloads, unzips and sets up MongoDB, Node and iField