Consistency in object tracking - PLPath vs Stack #5402
Replies: 18 comments
-
P[art]L[ocation]Path would not be appropriate for things that don't necessarily involve parts. |
Beta Was this translation helpful? Give feedback.
-
How about Storage Location Stack or Storage Location Path? |
Beta Was this translation helpful? Give feedback.
-
I like something simpler and clearer, ideally just "Location", or "Path"
(not very clear) or "Tree" ?
…On Mon, Jan 10, 2022 at 11:05 AM Teresa Mayfield-Meyer < ***@***.***> wrote:
* [EXTERNAL]*
In catalog records, the container stack is called PLPath
[image: image]
<https://user-images.githubusercontent.com/5725767/148815688-70b24a03-efb3-44ef-8a1f-87ee0e8e1c4a.png>
in the container history it is called Stack
[image: image]
<https://user-images.githubusercontent.com/5725767/148815920-eabdc23d-347d-42ac-933b-007ad21802db.png>
Stack in container history will show the last place the thing was before
it was moved (same as PLPath) let’s rename to make them consistent.
What does PLPath stand for and would we rather use "Stack" everywhere? Or
do neither of these terms do a good job of describing what they represent?
If not, what would?
@KyndallH <https://github.com/KyndallH> @campmlc
<https://github.com/campmlc> @Nicole-Ridgwell-NMMNHS
<https://github.com/Nicole-Ridgwell-NMMNHS>
—
Reply to this email directly, view it on GitHub
<#4239>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADQ7JBHYACB45T7AKMMKREDUVMNWPANCNFSM5LUJMGQA>
.
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:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I vote for either Whereabouts or Location. |
Beta Was this translation helpful? Give feedback.
-
I like location or storage location |
Beta Was this translation helpful? Give feedback.
-
Consensus seems to be "location" |
Beta Was this translation helpful? Give feedback.
-
I think the two "requirements" of this are:
"Tree" doesn't seem quite right - the branches have been stripped for this view. (The source data are certainly a "tree.") |
Beta Was this translation helpful? Give feedback.
-
PLocation?
…On Wed, Jan 12, 2022 at 11:58 AM dustymc ***@***.***> wrote:
* [EXTERNAL]*
I think the two "requirements" of this are:
1. Concise; lots of things don't have this information, the label
shouldn't take up unnecessary space.
2. Isn't overly confusing with
https://arctos.database.museum/info/ctDocumentation.cfm?table=ctspecpart_attribute_type;
eg "location" is likely to cause problems.
"Tree" doesn't seem quite right - the branches have been stripped for this
view. (The source data are certainly a "tree.")
—
Reply to this email directly, view it on GitHub
<#4239 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADQ7JBF3DQJBSSRSGZXOB7DUVXFN3ANCNFSM5LUJMGQA>
.
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:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Storage Path? |
Beta Was this translation helpful? Give feedback.
-
Depends what the "P" is for....
There's not necessarily anything stored there - this is for containers, whether they contain anything or not and whether that anything involves parts or not. I'm not sure there are any wrong answers, just some random considerations.... |
Beta Was this translation helpful? Give feedback.
-
I think Location is good and understandable in this context . . .
…On Wed, Jan 12, 2022 at 2:40 PM dustymc ***@***.***> wrote:
* [EXTERNAL]*
PLocation
Depends what the "P" is for....
Storage Path?
There's not necessarily anything stored there - this is for containers,
whether they contain anything or not and whether that anything involves
parts or not.
I'm not sure there are any wrong answers, just some random
considerations....
—
Reply to this email directly, view it on GitHub
<#4239 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADQ7JBGSMOOZ5653M76RJZ3UVXYLTANCNFSM5LUJMGQA>
.
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:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Part attributes display differently. |
Beta Was this translation helpful? Give feedback.
-
Object tracking group says lets go with location. |
Beta Was this translation helpful? Give feedback.
-
Assuming that doesn't cause some sort of conflict with the Part Attribute called Location. |
Beta Was this translation helpful? Give feedback.
-
It won't - all we are talking about are labels on the parts table (and in some other places) see #4239 (comment) |
Beta Was this translation helpful? Give feedback.
-
For machines: Not at all, it's a different context/thing. For people: Maybe? It's the same sort of information, sorta, and there's some "same name different thing" conversation somewhere that I can't find right now.... FWIW I'm fine with whatever. |
Beta Was this translation helpful? Give feedback.
-
How about ContainerLocation? Makes it different from the location attribute and matches up with the "InContainer" label |
Beta Was this translation helpful? Give feedback.
-
@campmlc @Nicole-Ridgwell-NMMNHS @KyndallH ContainerLocation ? |
Beta Was this translation helpful? Give feedback.
-
In catalog records, the container stack is called PLPath
in the container history it is called Stack
Stack in container history will show the last place the thing was before it was moved (same as PLPath) let’s rename to make them consistent.
What does PLPath stand for and would we rather use "Stack" everywhere? Or do neither of these terms do a good job of describing what they represent? If not, what would?
@KyndallH @campmlc @Nicole-Ridgwell-NMMNHS
Beta Was this translation helpful? Give feedback.
All reactions