{"_id":"54871b32b3441a1f00f20d7f","project":"54870ea47810260b001c36ab","category":{"_id":"548713247810260b001c36be","__v":5,"pages":["548777b6a8b5e31600952e49","54877841b3441a1f00f20edc","5487786fb3441a1f00f20edf","548aeff11bd6c40b00f777e7","548af0141bd6c40b00f777eb"],"project":"54870ea47810260b001c36ab","version":"54870ea57810260b001c36ae","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2014-12-09T15:20:04.035Z","from_sync":false,"order":2,"slug":"report-layout","title":"Report layout"},"version":{"_id":"54870ea57810260b001c36ae","project":"54870ea47810260b001c36ab","__v":20,"createdAt":"2014-12-09T15:00:53.237Z","releaseDate":"2014-12-09T15:00:53.237Z","categories":["54870ea57810260b001c36af","5487116f7810260b001c36b5","548711797810260b001c36b6","548711807810260b001c36b7","548713127810260b001c36bd","548713247810260b001c36be","548713aa7810260b001c36c0","548713c2f907080b00fc49d5","548713eef907080b00fc49d9","54871a0db3441a1f00f20d78","54871b15b3441a1f00f20d7e","54871cbeb3441a1f00f20d87","548817fac178b40b00aa2eec","558a6dd975eaf50d004e4bf5","558a6e37dbe5b63700f8d1fe","56795d8c07bf6a0d0083ee9e","583e9d764ced340f00b05a5c","5d1f3f70b4648901728803b7","5d22f7db4c9e14005111e34f","5d22fa62a541770012a07464"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"__v":5,"parentDoc":null,"user":"54870d54f907080b00fc49cd","githubsync":"","metadata":{"title":"","description":"","image":[]},"updates":["58877485e6687625009badef","588774a6b23c022d00acd116","588774c2c541933900c490c3","588774d5e3e762190098de77"],"next":{"pages":[],"description":""},"createdAt":"2014-12-09T15:54:26.809Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"try":true,"basic_auth":false,"results":{"codes":[]},"settings":"","auth":"never","params":[],"url":""},"isReference":false,"order":3,"body":"Reports generated with ArchiSnapper contain a list of observations, also called deficiencies, issues, or observations. Let's stick with the term 'observation'. Every observation in ArchiSnapper is assigned a number. Here we explain how this numbering works.\n\nSuppose we have a project XYZ for which we create a first field report. After syncing from our mobile/tablet the report appears in our online account. Suppose we have three observations (A, B, C) spread over 2 categories (CAT 1, CAT 2). Since this is the first report for this project, the numbering would be like this:\n\nCAT 1\n- Observation A (1.1)\n- Observation B (1.2)\n\nCAT 2\n- Observation C (1.3)\n\nWhen changing the order of the observations (or the order of the categories), the numbers will change to stay ordered ascending from top to bottom. Suppose we switch observation A and observation B from position, we'd have:\n\nCAT 1\n- Observation B (1.1)\n- Observation A (1.2)\n\nCAT 2\n- Observation C (1.3)\n\nFYI, it's also possible to change the default order of the categories. You can manage this in the 'categories' screen of your online account. This order will be applied everywhere.\n\nNow, suppose we make a second report for this project. When making a new report we always have two options: start from scratch, or start from the previous report.\n\nWhen starting from scratch the numbering will be exactly the same as in the previous example, only will we now have 2.1, 2.2, ... as numbers (as it's the second report for this project).\n\nWhen starting from the previous report, the observations of the last report will be used as a starting point and we can edit those observations and add new observations. Suppose we add two observations: observation D for CAT 1 and observation E for CAT 2:\n\nCAT 1\n- Observation B (1.1)\n- Observation A (1.2)\n- Observation D (2.1)\n\nCAT 2\n- Observation C (1.3)\n- Observation E (2.2)\n\nHere again, when changing the order of the new observations (2.1, 2.2, ...), the numbers will change so the observations are numbered ascending from top to bottom. The numbers for the cloned observations are fixed and will not change when switching position.\n\nConclusion: observations get a number based on the report number for this project and their position in the report (cf ascending from top to bottom). For new observations, the numbers are changed when changing the positions. For cloned observations - when starting from a previous report - the numbers are not changed when changing the positions.\n\nOne more free tip: it's also possible to manually change the report number of a report. Example: you create a first report with ArchiSnapper, for project XYZ. The report number will be XYZ-1. You can change this number (to for example XYZ-7) when editing the report online and all new observations for this report will be automatically re-numbered (7.1, 7.2, ...).","excerpt":"","slug":"how-remark-numbering-works-with-archisnapper","type":"basic","title":"How observation numbering works with ArchiSnapper"}

How observation numbering works with ArchiSnapper


Reports generated with ArchiSnapper contain a list of observations, also called deficiencies, issues, or observations. Let's stick with the term 'observation'. Every observation in ArchiSnapper is assigned a number. Here we explain how this numbering works. Suppose we have a project XYZ for which we create a first field report. After syncing from our mobile/tablet the report appears in our online account. Suppose we have three observations (A, B, C) spread over 2 categories (CAT 1, CAT 2). Since this is the first report for this project, the numbering would be like this: CAT 1 - Observation A (1.1) - Observation B (1.2) CAT 2 - Observation C (1.3) When changing the order of the observations (or the order of the categories), the numbers will change to stay ordered ascending from top to bottom. Suppose we switch observation A and observation B from position, we'd have: CAT 1 - Observation B (1.1) - Observation A (1.2) CAT 2 - Observation C (1.3) FYI, it's also possible to change the default order of the categories. You can manage this in the 'categories' screen of your online account. This order will be applied everywhere. Now, suppose we make a second report for this project. When making a new report we always have two options: start from scratch, or start from the previous report. When starting from scratch the numbering will be exactly the same as in the previous example, only will we now have 2.1, 2.2, ... as numbers (as it's the second report for this project). When starting from the previous report, the observations of the last report will be used as a starting point and we can edit those observations and add new observations. Suppose we add two observations: observation D for CAT 1 and observation E for CAT 2: CAT 1 - Observation B (1.1) - Observation A (1.2) - Observation D (2.1) CAT 2 - Observation C (1.3) - Observation E (2.2) Here again, when changing the order of the new observations (2.1, 2.2, ...), the numbers will change so the observations are numbered ascending from top to bottom. The numbers for the cloned observations are fixed and will not change when switching position. Conclusion: observations get a number based on the report number for this project and their position in the report (cf ascending from top to bottom). For new observations, the numbers are changed when changing the positions. For cloned observations - when starting from a previous report - the numbers are not changed when changing the positions. One more free tip: it's also possible to manually change the report number of a report. Example: you create a first report with ArchiSnapper, for project XYZ. The report number will be XYZ-1. You can change this number (to for example XYZ-7) when editing the report online and all new observations for this report will be automatically re-numbered (7.1, 7.2, ...).