Hello, I am new to S123 and am using portal for my feature services and using them to create surveys...this is my first survey and I thought I would use a hobby, being a Purple Martin landlord (for several years now) to conduct nest checks and collect associated data from the housing colony (unit)...the data base flow is Housing Units (point), usually one landlord per housing unit, but could be many if ownership changes hands, so 1 housing unit to many landlords, many nesting cavities per housing unit, usually one nesting pair per cavity (could be 1 to 1) but can be multiple of the pairs fail and others move in so 1 cavity to many pairs (just in case)...and many nest checks per nesting cavity...so why the use of 1-M on tables that might rarely change...I truly believe in normalization and only appending new records when something changes...keeps a chain of custody of records for historical purposes...it makes life harder to build the table but i would rather have that history
So the survey(s) is based on the feature service in portal published from a FGDB in ArcMap....The geopoint feature class (Housing Units) that is related to 4 child tables (1-M)...3 of the child tables (Landlord_tbl, NestingCavities_tbl, BirdPair_tbl) are descriptive attributes for different groups of data (normalized)...the 4th table (NestChk_tbl) is the inspection table and will have many records...I will build surveys for the other tables but likely won't use them, those tables already have the data I need for now, but may need them in the future...next season (2021) bird pairs will be new records so I will use that survey more often, even now if a bird pair changes cavities or is replaced, but the main survey for use will be nest checks
Here is my question: For the nest check survey...I want to be able to scan a QR code (that i have placed on each nest cavity) for NestCavityID into the Cavity ID answer field, (what I want) this in turn will display some of the corresponding parent field data like OwnerID, HousingUnitID, City, State, ZIP (HousingUnits_tbl) etc and maybe a diagram (image) of the NestCavity placement...I want this information to be read only.......The idea is that the field collector using the survey will be able to verify or have a visual cue of some kind instead of solely relying on the barcode scan entry, they can be sure they are doing the nest check for the correct cavity (because we all know scanners don't ever have erroneous reads)...I understand this can be done with pull data from a csv...or other functions, using collector and a custom URL..
As of now there are very few geopoints (ONE! to be exact) so I don't want to have to (or need to use) collector in the workflow right now (this season)...I can do pulldata with the CSV, but my question is? When that data is pulled into the answer fields will that data be added somewhere (back to the parent tables) when the survey is submitted?...basically I just need the data as a visual reference for the field user and not be collected data, as it already sits in a related table...
Why am I overbuilding the capability? In the future if I start collecting data in many housing units with many landlords over a wide geographic area, I can then think about using the collector to S123 workflow...
I am also still trying to figure out how I will create the queries and reports that I need for this project...but that is a battle for a different day...I am just trying to get the ball rolling with nest checks (I have them on paper now and would like to start entering the backlogs as well as start using Survey on my iphone to conduct the nest checks)
Any help would be greatly appreciated! Thanks!