fixes #902 and #901 here are the functions which @carolrose wrote with some of my guidance :) now they will be availible in everyone's corpus so that if they want to, they can also use the cleaning example to make their own cleaning examples. eventually if people use these we can make data lists in the app that the user can interact with, without having to be a power user. like having a perpetual list of data taht should be cleaned for animicy etc... ask @hisakonog for details
for #903 i added a map reduce that will amke it so we can use a url like this to get all teh datum in one session,  https://corpusdev.lingsync.org/public-firstcorpus/_design/pages/_view/get_datums_by_session_id?key=%223C216AAE-C506-478D-B426-CEEF0CA3F270%22
fixes #903 i added a link the user can click on which will show them all the data in sessions with the same goal, i think this request comes from alan or someone orginally, so the only info i have is 'Would be useful to have access to all the data' im not sure if they want this because they want to see the datum with that goal, or if they want to see datum in that session. why would you want to see datum in that session. linguistically its because you are looking for similar datum, so goal is the best way to search for it. if you are doing it as an audit to a corpus, and you need to see exactly which datum are in that session we do have a url for that, so it is posisbel to change the behaviour of this new link to work like that. alternatively, we could add a data list into a session so that the user can see the data there. but im not sure we want them to get confused about the difference betwen data lists and sessions (like gretchen was in the beginning). session is just static data that you dont want to type over and over again for each datum because they share the same speaker, dialect date you colelcted it, and goal for the original collectino of the datum...
making unicode minimized by default fixeses #904
pretty sure we should use doc._id as a key, rather than the collection. these were made by copying from a sample backbone couchdb project in #812
reverting #781 and #791

the Andika font is too close to comic sans, considered a taboo font for webapps. trying headland one
here is another alternative for #781 and #791 it is called Gentium Basic
making the in uppercase
have to use https to get the font
fixes #905 found that the data lists had zebra on them which was making the datum's spans show up with an odd white background
fixes #907 and #906

added a new machine field called syntacticCategory which will be used for cleaning and search but not necessarily somethign that most users will use. it is hidden all of the time andonly visible if you click on the show rare fields button. also modified the new corpus logic to not copy the datum fields if you making a new corpus from the firstcorpus (a practice corpus where we expect people to have garbage that they dont want. later for #806 we will make a dropdown with a set of tempaltes that the user can choose...ie, language community, linguist, corpus linguist, phonetician etc
minifying and preparing for release v1.46
fixes #880 i think , sometimes if your corpus buildign fails in some way, you end up on the corpus page and it has no datalists or sessions to show you on the dashboard. if you are on the corpus page and you are lacking either sessions or datalists, it will tak eyou to your user page. where you can click on the corpus, and it will generate everything for you if stuff is missing.
adding the ° symbol so we can use it in the syntactic categories line for #906
minifiying for release
making nicer offline error message
upping to version 1.46
Merge pull request #908 from cesine/master

Change list for v1.46


released in LingSync Testing v.1.46