nicknames for numbered entities in the recording system #1236
Replies: 4 comments 7 replies
-
And I still agree with that initial thinking. One assigns nicknames because one thinks (sometimes erroneously) that they'll be more intuitively unrepeated than normal numbering systems. A question for this is not just where they are created but also where they are used and displayed. I can imagine a configuration setting that allows for choosing whether or not units show up from the start page as numbers or as nicknames, for instance. Gallery searches. But what about locus lists? You may call the unit Oscar the Grouch, but do you call the locus Oscar the Grouch-003? |
Beta Was this translation helpful? Give feedback.
-
@lrn5 Leah you are on here! I just didn't have your proper handle. This should send you an email, since I've tagged you, and then you can go ahead and add comments about nicknaming at Samothrace here - I am quite curious to hear more. |
Beta Was this translation helpful? Give feedback.
-
Yeah totally and that is one reason why I don't always manage to hide my frustration with nicknames :) But it's also where a system can help. If there is ever anywhere where things are referred to without their proper name/identifier, where they are just nicknames, then in the formal record it makes sense to include nicknames attached to the proper identifier. So that someone in future can sort it out when the memory is gone. |
Beta Was this translation helpful? Give feedback.
-
Hmm, we have many nicknames for restaurants, stores, and people (all good and well until we need to make a reservation and can’t remember the actual names of places…), but I can’t think of any for numbered contexts. We do have some rooms that we refer to by functional name rather than by number (e.g. biclinium instead of Room 40), but these should all be cross referenced in multiple plans and context sheets.
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 Oct 16, 2021, at 3:59 PM, lbestock ***@***.***> wrote:
Univocality strikes me as one of the defining features of our dysfunctional era.
Instinctive?
And I did not think I was bashing nicknames. Oscar the Grouch was always one of my favorites. @cmrice-arch <https://github.com/cmrice-arch> and @Tfranconi <https://github.com/Tfranconi> do you guys nickname things? As in, do you call Area 7 "Red Room" or such when you're speaking to each other about it? And/or in notes somewhere? (Might be a bad example, get away from the example.) The question arose really because of a project who did have numbers for their units, but never referred to them by number, always by names. If you do use nicknames, for what?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#1236 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQHJCGPUEITK5MSTFNWXG7DUHHKQVANCNFSM5GDQ5WJQ>.
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>.
|
Beta Was this translation helpful? Give feedback.
-
Moved here from "ideas and drafts for the recording system" in the wiki:
At both the unit level and the collected material level people assign something like a nickname, or an alternate way of referring to things, that seems to be so instinctual that fighting it is counter-productive. So we have begun to discuss how to make it regular, so that nicknames are not repeated, for instance. Examples were Leslie's use of Sesame Street names for her units, and Miriam's use of MM numbers for her samples (which she abused - MM4 was used for two URAP numbers, which is precisely why this conversation got started). Our initial thinking is that we should not use a shopping basket method for insuring lack of doubled use, but rather that it is pretty unlikely something would be double assigned and we should ask synchronization to catch it if that happens instead.
Beta Was this translation helpful? Give feedback.
All reactions