Latest Contributions by Katie_Clark

You can access it through here:   ... View more

I agree with Josh, it sounds like a method very prone to user error, and I can't think of a benefit to having a multiline question here. I would recommend having unique questions in your survey that are integer or decimal type, and then you can use those fields in calculations in the survey to determine the ratio.  ... View more

I attached the XLS form, and here are the Javascript functions I embedded in the survey.    function uniqueSpecies (translatedSpecies) { var x = translatedSpecies x = Array.from(new Set(x.split(','))).toString(); return x; } function translateSpecies (batString) { var text = batString; var result = text.replace(/ANPA/g, " Pallid bat"); var result = result.replace(/COTO/g, " Townsend's big-eared bat"); var result = result.replace(/EPFU/g, " Big brown bat"); var result = result.replace(/LABL/g, " Red bat"); var result = result.replace(/LACI/g, " Hoary bat"); var result = result.replace(/LANO/g, " Silver-haired bat"); var result = result.replace(/MYCA/g, " California myotis"); var result = result.replace(/MYEV/g, " Long-eared myotis"); var result = result.replace(/MYTH/g, " Fringed myotis"); var result = result.replace(/MYVO/g, " Long-legged myotis"); var result = result.replace(/MYYU/g, " Yuma myotis"); var result = result.replace(/PAHE/g, " Canyon bat"); var result = result.replace(/TABR/g, " Mexican free-tailed"); var result = result.replace(/MYLU/g, " Little brown myotis"); var result = result.replace(/MYCI/g, " Small-footed myotis"); var result = result.replace(/NYMA/g, " Big free-tailed bat"); var result = result.replace(/EUPE/g, " Western mastiff bat"); var result = result.replace(/EUMA/g, " Spotted bat"); var result = result.replace(/MY/g, " Myotis spp."); return result; }     This might be a helpful references for you: https://community.esri.com/t5/arcgis-survey123-blog/extending-survey123-smart-forms-with-custom-js/ba-p/898782  Also, I didn't do this in my XLS form because I was just testing, but remember to set the bind::esri:fieldType to Null for all of these Javascript and display fields if you don't want these fields to be part of your feature layer attribute table. Also, the fields that are used in the calculations can have "hidden" set as the appearance type so they won't display in the survey.  I really hope this helps! And if anyone else comes across this and has pointers, I'm all ears. I came up with this solution as a complete newbie to Javascript (~intermediate familiarity with Python) and referenced StackOverflow a lot... ... View more

One solution I might suggest is to unshare the surveys so that only the owner and admins will see them. It's not exactly the same as a true "archive", but it will help clear up the clutter for users who aren't admins. I'm not aware of any other type of formal archiving process in AGOL. ... View more