PACHA: Questions and topics for meeting on 03/10/2022

[urapadmin]

@urapadmin, @lbestock, @nparkervan: collecting topics for our next meeting here as they come up:

• does Parker get GitHub messages? he does not really.
• clarify elevations and coordinates. #1380
• reporting - what do the authorities require and what does Parker expect from the system on this front?
• talk about deposit details: #1419

• 1387

• discuss and clarify workflow specification document that will serve as the basis of configuration
• what data of the former season does Parker want imported and how important is that at all?
• i18N gets a bit less likely each day since time is ticking so fast and reporting is big. It might still be happening but I want to rae the real possibility that the whole thing will be in English
• drawing (photo) numbers: #1446 I am planning to introduce a sequential (but not gap-less) automatic number assigned on synchronization (so not in the field). Are drawing (photo) numbers used in PACHA and would that still be necessary the same way now that photos can be imported to be context-bound? What were the rules for that number?

[urapadmin]

results of meeting on 03/10/2022:

• does Parker get GitHub messages?

he does not really, at least not when just mentioned via @. I have made him an assignee now.

what do the authorities require and what does Parker expect from the system on this front?

Parker sends a sample of their former reporting

• 1387

Parker sends something to the google drive

• [x] discuss and clarify workflow specification document that will serve as the basis of configuration

➡️ Laurel's notes

we didn't get to these:

• [ ] what data of the former season does Parker want imported and how important is that at all?
• [ ] i18N gets a bit less likely each day since time is ticking so fast and reporting is big. It might still be happening but I want to raise the real possibility that the whole thing will be in English
• [ ] drawing (photo) numbers: #1446 I am planning to introduce a sequential (but not gap-less) automatic number assigned on synchronization (so not in the field). Are drawing (photo) numbers used in PACHA and would that still be necessary the same way now that photos can be imported to be context-bound? What were the rules for that number?

• clarify elevations and coordinates. #1380
• talk about deposit details: #1419

we'll discuss that when the first version is out

[nparkervan]

I got this!

On Thu, Mar 10, 2022, 6:30 PM urapadmin @.***> wrote:

@urapadmin https://github.com/urapadmin, @lbestock https://github.com/lbestock, @nparkervan https://github.com/nparkervan: collecting topics for our next meeting here as they come up:

• does Parker get GitHub messages? he does not really.

what do the authorities require and what does Parker expect from the system on this front? Parker sends a sample of their former reporting

• 1387 https://github.com/arch-kiosk/arch-kiosk-office/issues/1387

  Parker sends something to the google drive

• discuss and clarify workflow specification https://docs.google.com/document/d/1Dk6truLtnCSNiCnt13lfIqvcxaiLMb6ozzK_fvcA7eg/edit document that will serve as the basis of configuration Laurel's notes

we didn't get to these:

• what data of the former season does Parker want imported and how important is that at all?

• i18N gets a bit less likely each day since time is ticking so fast and reporting is big. It might still be happening but I want to raise the real possibility that the whole thing will be in English

• drawing (photo) numbers: #1446 https://github.com/arch-kiosk/arch-kiosk-office/issues/1446 I am planning to introduce a sequential (but not gap-less) automatic number assigned on synchronization (so not in the field). Are drawing (photo) numbers used in PACHA and would that still be necessary the same way now that photos can be imported to be context-bound? What were the rules for that number?

• clarify elevations and coordinates. #1380 https://github.com/arch-kiosk/arch-kiosk-office/issues/1380

• talk about deposit details: #1419 https://github.com/arch-kiosk/arch-kiosk-office/issues/1419 we'll discuss that when the first version is out

— Reply to this email directly, view it on GitHub https://github.com/arch-kiosk/arch-kiosk-office/issues/1451#issuecomment-1064620515, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB2IPBZS5KSO6FJPFOX4EYTU7KA2NANCNFSM5QBRFNYQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

[urapadmin]

Thanks for letting me know.