-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change help text at top of Agent Search page #3813
Comments
Well - I am not sure we have actually agreed to use this for entities or organisms...... |
We're looking at Kianga again and after today's meeting, I am coming around to this idea of a dashboard for agents.... and especially if we add in collections as agents! |
BUT - I don't think we want a bunch of "organisms" mixed in? Or maybe we do. Eventually we could have "pocket mouse #1" as an agent..... The functionality is perfect, but I think we might consider keeping people and organizations separate from other organisms. If everyon is OK with them being together, then we at least need some new agent types.... |
Absolutely not, at least without discussion and new agent types, and the existing non-human Agents should be removed. FWIW the things that have been asked for in Entities are the things that cataloged items have always done; I think we rushed Entity creation (and it's not been much used, but perhaps we'd have not known without doing something), and that we should remove the "entity node" and transfer any useful functionality to #1966 (comment), both as a matter of "corectness" and of sustainability. |
I am not sure I agree with this assessment - clearly, the things we are seeking in an entity are the things that agents do.... |
ah, yea, organism is way too vague.
But I would say we may want to track George the pocket mouse if it's an
experimental animal with lots of separately cataloged biopsies (just not
the organism pocket mouse.
I think we need to review the other_agents -- most of those are organisms
or groups, not 'other agents'. Or just badly informed agents (initials
only). What is 'other_agent' if not a non-human agent?
Let's roll this issue into a broader discussion on tracking living
collections and cultural/ archival collections.
…On Thu, Aug 5, 2021 at 3:42 PM Teresa Mayfield-Meyer < ***@***.***> wrote:
things that have been asked for in Entities are the things that cataloged
items have always done
I am not sure I agree with this assessment - clearly, the things we are
seeking in an entity are the things that agents do....
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3813 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATH7UO7HAYGLIDU5RGBV2TT3MHTXANCNFSM5BUXRADQ>
.
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&utm_campaign=notification-email>
.
|
They don't have bulk tools, catalog records do. They don't have identifications, certainly not those backed by taxa, catalog record do. They don't have more than "this is me" 'other id' functionality; catalog records do. They cannot hold attributes; catalog records can. They don't have mature tools supported by a broad user group: #3765 More stuff that existing bulk tools handle: #3685 I'm sure there's more, but I'm having a lot of difficulty nailing down anything in any of the discussions that can happen within Arctos and is not handled by catalog records. Anything we do to make relationships between or bulk tools for catalog records more functional works for many use cases. (Anything we do with Entities will work for only limited use cases.) If there's a disadvantage it's that catalog records of type {something new and appropriate} might look like an independent Occurrence, but if we're cataloging critter-at-place-and-time we're already doing that (and relying on users to recognize it) - again, any work towards making that more clear will have broad impacts. |
Many can be deleted - #882 has been hanging around way too long, it needs implemented and documentation needs updated. Most seem to be miscategorized people, organizations, and groups - https://arctos.database.museum/info/ctDocumentation.cfm?table=ctagent_type
|
i think you're overthinking this. You're right all those things are cat_items and no issues there. beyond the normal relating of specific records to each other how can people find an individual and all their Arctos records? Here's an example of all this chimpanzee's samples, its wikidata page, all id's in one manageable, query-able, understandable page. |
If that's all you want, then there should be (have been) a discussion about agent type - this is clearly a different THING, and Arctos users have complained about finding this there. If you want to do things that Agents can't do, then it's the wrong data object (and I can't understand the requests to do those things). |
how reliable is Agent Activity report?
https://arctos.database.museum/agents.cfm?agent_id=10000002
if there are no data dependencies, ok to delete?
Maybe @***@***.***
***@***.***> or @cynthia
Carr ***@***.***> could help too?
…On Thu, Aug 5, 2021 at 4:12 PM dustymc ***@***.***> wrote:
review the other_agents
Many can be deleted - #882 <#882>
has been hanging around way too long, it needs implemented and
documentation needs updated.
Most seem to be miscategorized people, organizations, and groups -
https://arctos.database.museum/info/ctDocumentation.cfm?table=ctagent_type
create table temp_other_agent as select preferred_agent_name from agent where agent_type='other agent' order by preferred_agent_name;
temp_other_agent.csv.zip
<https://github.com/ArctosDB/arctos/files/6942060/temp_other_agent.csv.zip>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3813 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATH7UOFYLUMAMHJOV3537TT3MLFDANCNFSM5BUXRADQ>
.
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&utm_campaign=notification-email>
.
|
yep, we should clean up other_agent, discuss a definition for it, possibly
explore a better and new agent type for this use.
No new things that Agents cant do, so might be simply an interface issue
(eg., separate search for people and orgs and another for whatever else is
that those two things)
…On Thu, Aug 5, 2021 at 4:24 PM dustymc ***@***.***> wrote:
If that's all you want, then there should be (have been) a discussion
about agent type - this is clearly a different THING, and Arctos users have
complained about finding this there.
If you want to do things that Agents can't do, then it's the wrong data
object (and I can't understand the requests to do those things).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3813 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATH7UIXLTKVWKXRM7XXRJDT3MMRBANCNFSM5BUXRADQ>
.
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&utm_campaign=notification-email>
.
|
I like the idea of adding a new agent type and suggest: organism - any non human organic, living system that functions as an individual entity. Wikipedia. Humans should be assigned and agent type of person, group or organization. Honestly - I have never even looked at other-agents and a bunch of them should be organizations and yes, a bunch really are projects and not agents unless they can be changed to groups and all the person agents who were on the expedition are added. (Even then they probably should have associated projects). Can we get a list of them so we can put them in a sheet and make bulk decisions about what to do with them? |
I will also push back on this. An agent could be super useful for unnamed and non-experimental animals that have parts at MSB and other parts at UAM. But now as the project discussion proceeds, I wonder if a project might not be a better place for this....Let's see. |
No to the projects as stuff for any given organism might come in with lots of other junk in any given accession (no way to associate "contributed by" easily and only get stuff for one organism. |
The only issue with the agent model is filling up the agent table with a bunch of Mexican Wolves and eventually unnamed mice and trees. But I think we can work it out with a new agent type ("entity" or "organism") and use the UI to separate them when searching (a search page for all "person" agents and a search page for organisms which are effectively the same page, but you get on or the other depending upon which menu item you pick). The other rub will be, in order to keep this stuff normalized, we will need to get rid of the other id "organism ID" and any time you have a part of something that is also at Smithsonian, we will need an "organism" agent in Arctos to create that "organism ID" kind of linkage when the data goes out to aggregators (the beauty of that is that Smithsonian could put our agent url in their "organism id" and BOOM GBIF knows they are the same organism!). Which means we will need a new "collector" (that really needs renaming) role. Something like entity. And the agent url is what would get passed via DarwinCore as OrganismID. In a way, this will make us an identifier for organisms which is crazy, but until there is an "organism registry" somewhere, I don't see how we can do any better. |
Discussed during Agent Committee meeting. Although there are currently organisms in agents, with the many discussions about this topic in AWG and the Agent Committee, a solution will come about in which organisms will not be in the agent page. Agents/organizations should be separate from organisms/specimens, and updating the description will not create clarity, but instead confusion. |
The current text is a wee bit confusing and does not include all the agent types we are now tracking. We suggest to replace the text with the following:
The text was updated successfully, but these errors were encountered: