ELRI: Task list for first season

[urapadmin]

This is the list of things to do for ELRI (Economic Landscapes of Roman Istria)

• [x] set up online kiosk
• [x] first configuration according to the context sheet and comments we got
• [x] #2661
• [x] @lbestock configures lists and terms
• [x] @urapadmin configures ID methods
• [x] @urapadmin please delete all locus types EXCEPT: deposit, fill, cut, structural.
• [x] Kiosk: custom settings for colours etc.
• [x] Kiosk: custom settings for regex if needed
• [x] What is the exact timing? ELRI is first, then USTP then AAC? Will Candace come back between ELRI and USTP? I hope so.
• [ ] #2684
• [x] #2654
• [x] #2655
• [x] "pottery" opens up the ceramics preprocessing.
• [x] "show_material_specified" -> nope
• [x] "label_sector" -> "area"
• [x] #2656
• [x] #2657
• [x] #2659
• [x] #2660
• [x] #2670
• [x] SOS software: install and test on the Loaner Mac.

[lbestock]

A few notes on configuration after a zoom with Candace and a discussion at Hillside. @lbestock will handle terminology @urapadmin will handle numbering, which is a hybrid between USTP and URAP: context numbers are independent of unit numbers, but CM numbers are sequential numbered within a context (no independent number runs for bulk/special finds/samples). @urapadmin will also handle ceramics, which should have preprocessing in the same way as USTP.

Meeting with @cmrice-arch 10am Wednesday 25 IV 24, by which time we will have a configured online system to walk through.

[urapadmin]

what about the "void" locus type? Did you add that but it isn't needed? I delete it.

[urapadmin]

so:

• trenches are free input
• loci are numbers dependent on a predefined number list. No prefix or suffix, 4 digits fix.
• collected materials are numbered sequentially on the basis of their locus. No prefix or suffix. no number of digits: starts with context-1

[urapadmin]

as for timing:

I’ll be back from Croatia on May 25 and can swap out iPads before heading to Italy on June 8 or so if necessary.

[cmrice-arch]

I don’t think I’ve asked this yet — what is the setup for designating context numbers by trench?

__ Candace M. Rice Assistant Professor of Archaeology and Classics

Joukowsky Institute for Archaeology and the Ancient World Brown University | Box 1837 | 60 George Street | Providence, RI 02912 | USA

On Apr 23, 2024, at 11:31 AM, kioskadmin @.***> wrote:

so:

trenches are free input loci are numbers dependent on a predefined number list collected materials are numbered sequentially on the basis of their locus — Reply to this email directly, view it on GitHub https://github.com/arch-kiosk/arch-kiosk-office/issues/2650#issuecomment-2072717748, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQHJCGJ3RHM43TB7A364H23Y6Z5ERAVCNFSM6AAAAABGTXAIA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZSG4YTONZUHA. You are receiving this because you were mentioned.

[urapadmin]

I don’t think I’ve asked this yet — what is the setup for designating context numbers by trench?

4 digits based on a preassigned numbering list, as in USTP. So starts with 0001 for a first device and with whatever you choose, e.g. 0100, for device 2.

[lbestock]

@cmrice-arch The 4 digits is what we configured so far for you. But, it's very easy to have context numbers that are sequential by trench (which is what we do at Uronarti). Then you have say Trench AA, and contexts would be AA-001, AA-002, AA-003 etc. Do you know what naming convention you will use for trenches? (It isn't even necessary to decide that yet if you would prefer this numbering. We can set it so it is just "trench name"-001, etc.)

[cmrice-arch]

We’ll number trenches: Trench 1, Trench 2, etc. We’d like to aim for context numbers that make it obvious which trench they are from, even if there is no additional info.

__ Candace M. Rice Assistant Professor of Archaeology and Classics

Joukowsky Institute for Archaeology & the Ancient World Brown University | Box 1837/ 60 George Street Providence, RI 02912 401-863-3710

On Apr 23, 2024, at 2:06 PM, lbestock @.***> wrote:

@cmrice-arch https://github.com/cmrice-arch The 4 digits is what we configured so far for you. But, it's very easy to have context numbers that are sequential by trench (which is what we do at Uronarti). Then you have say Trench AA, and contexts would be AA-001, AA-002, AA-003 etc. Do you know what naming convention you will use for trenches? (It isn't even necessary to decide that yet if you would prefer this numbering. We can set it so it is just "trench name"-001, etc.)

— Reply to this email directly, view it on GitHub https://github.com/arch-kiosk/arch-kiosk-office/issues/2650#issuecomment-2073063055, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQHJCGNY3WWKK7EIYL6JDH3Y62PJ3AVCNFSM6AAAAABGTXAIA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZTGA3DGMBVGU. You are receiving this because you were mentioned.

[cmrice-arch]

Does this work to add @amclean6787 to the thread?

[lbestock]

Andrew, let us know it works by responding! But it should. So, would you like "Trench 1-001" etc or "1-001"? Or "T1-001". I totally agree (having arrived at the same solution for my own work after not having had it for decades) that using the trench as a prefix for context numbers is the best combination of succinct and functional/meaningful.

[amclean6787]

Andrew, let us know it works by responding! But it should. So, would you like "Trench 1-001" etc or "1-001"? Or "T1-001". I totally agree (having arrived at the same solution for my own work after not having had it for decades) that using the trench as a prefix for context numbers is the best combination of succinct and functional/meaningful.

Yes, it seems to have worked! From my side, "T1-001" looks best, but any of the options would be good

[cmrice-arch]

I was also going to say T1-001, but looking at it in writing now that the coffee is kicking in, it occurs to me that we should keep it strictly numerical in the interest of a bi-lingual team. The Croatian word for trench is sonda, so the T might just cause confusion.

[amclean6787]

Very good point. Happy to keep it numerical

[urapadmin]

@lbestock This is not how we configured it, or did we? The context numbers are currently not related to the trench. If we relate them to the trench we won't need the identifier lists to assign the context numbers.

[lbestock]

I have to check. We originally configured it to need identifier lists. I changed that either while talking to Candace or before, but I can't remember if I synchronized this.

[urapadmin]

@luizaogs Can you please check if the things that are marked as checked on top (the ones that don't have their own ticket and that you can actually test) are actually working? I fear it will be overlooked otherwise.

[luizaogs]

Yes, they look fine to me.

[lbestock]

@lbestock This is not how we configured it, or did we? The context numbers are currently not related to the trench. If we relate them to the trench we won't need the identifier lists to assign the context numbers.

Yup - this is all properly configured. ELRI is ready to put on the local server for testing!

[urapadmin]

then I'll do that

[urapadmin]

@luizaogs: If you still have a nerve, could you please click through Q&V on ELRI (you would have to create records first) and test the terminology in Q&V in ELRI? So names for locus, unit, collected material, dayplans and check if they are plausible? If you encounter URAP terminology or strange variable expressions (something like '#(constants/bla bla)' instead of proper English, please let me know where. This is really not crucial, so don't wreck any of your weekend because of it.

[urapadmin]

@arch-kiosk/test I leave ELRI online for testing purposes. But the data is now safely transferred, so you don't have to treat the online system as a production system anymore. Meaning: You can create test data as you wish, I'll replace it later again.

[luizaogs]

@luizaogs: If you still have a nerve, could you please click through Q&V on ELRI (you would have to create records first) and test the terminology in Q&V in ELRI? So names for locus, unit, collected material, dayplans and check if they are plausible? If you encounter URAP terminology or strange variable expressions (something like '#(constants/bla bla)' instead of proper English, please let me know where. This is really not crucial, so don't wreck any of your weekend because of it.

Yeah, I can do this tonight. Currently suffering through a volume on gender in Spanish.

[luizaogs]

@urapadmin terminology in Q&V looks fine and matches that in FM.

(there's also a cat picture in there for you, if your covid brain desires one)