-
-
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
AWG Code Table Administrator #1597
Comments
I support this.
…On Thu, Jul 5, 2018, 5:57 PM Teresa Mayfield ***@***.***> wrote:
I propose that we add the position "Code Table Administrator" to the AWG.
It should not take two months to get parts, attributes, or other code
table items added. Requests for these types of additions often go unnoticed
which means that someone is not getting their data in or they are using
less-than-perfect means to do so. I think it would be good to have at least
three people responsible for monitoring the GitHub for these kinds of
requests and assisting with getting them cleared up. We also need to make
sure we have some good guidelines for such additions written in the
documentation so that we don't just start adding things willy-nilly without
definitions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1597>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOH0hAnSK0P5Tj0-ioGADWG3akPcnDOzks5uDovIgaJpZM4VEmMx>
.
|
From AWG meeting:
Any opposition to creating a Group Agent in Arctos and adding all who have code table access to it? |
No objection to group agent. As Co-Chair I have access and I believe Carla
does too. Anyone else?
…On Thu, Jul 12, 2018 at 3:38 PM, Teresa Mayfield ***@***.***> wrote:
From AWG meeting:
Who has access to Code Tables? Add/Change CT info
-when issues come up, we know who to ask to follow up
-CT Label / Assignment link so folks who can do this can keep track
-remove this task from Dusty - CT editors as distinct group
Shared table monitors who volunteer to help fix problems, review bad/low
data reports (e.g., agents, geographies, etc.)
Any opposition to creating a Group Agent in Arctos and adding all who have
code table access to it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1597 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOH0hEuj-fyWfeeMMz4b8A0e6DdkixiFks5uF6W7gaJpZM4VEmMx>
.
|
I also set up a team on GitHub. @ArctosDB/arctos-code-table-administrators so that people filing issues can tag you all. Please add anyone else who should be on the list. |
I have access to code tables but have refrained from using it.
______________________________________________________________
Jonathan L. Dunnum Ph.D.
Senior Collection Manager
Division of Mammals, Museum of Southwestern Biology
University of New Mexico
Albuquerque, NM 87131
(505) 277-9262
Fax (505) 277-1351
MSB Mammals website: http://www.msb.unm.edu/mammals/index.html
Facebook: http://www.facebook.com/MSBDivisionofMammals
Shipping Address:
Museum of Southwestern Biology
Division of Mammals
University of New Mexico
CERIA Bldg 83, Room 204
Albuquerque, NM 87131
________________________________
From: Mariel Campbell <notifications@github.com>
Sent: Thursday, July 12, 2018 1:43:39 PM
To: ArctosDB/arctos
Cc: Subscribed
Subject: Re: [ArctosDB/arctos] AWG Code Table Administrator (#1597)
No objection to group agent. As Co-Chair I have access and I believe Carla
does too. Anyone else?
On Thu, Jul 12, 2018 at 3:38 PM, Teresa Mayfield ***@***.***> wrote:
From AWG meeting:
Who has access to Code Tables? Add/Change CT info
-when issues come up, we know who to ask to follow up
-CT Label / Assignment link so folks who can do this can keep track
-remove this task from Dusty - CT editors as distinct group
Shared table monitors who volunteer to help fix problems, review bad/low
data reports (e.g., agents, geographies, etc.)
Any opposition to creating a Group Agent in Arctos and adding all who have
code table access to it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1597 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOH0hEuj-fyWfeeMMz4b8A0e6DdkixiFks5uF6W7gaJpZM4VEmMx>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#1597 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AQengxNYiZsO89uXHpDZwq2bX5ARq8y3ks5uF6brgaJpZM4VEmMx>.
|
See eg #1451 (comment). I don't think most users can manage Issues enough to properly tag anything, so the new team seems like unnecessary complication. Alternatively, we could give more people code table access - authority changes are emailed out, we're all carefully reviewing that (right!?!), so maybe it's OK if eg, all active AWG members can create authority values (which are then reviewed via the email). #1450 is critical to any approach. We can't possibly tell if a new value is actually new when there are undocumented existing values. It should not be possible to add or edit values without providing documentation, but it's certainly possible to provide useless documentation. Code table documentation is http://handbook.arctosdb.org/how_to/How-to-Use-Code-Tables.html |
Can github send email when a {project/label/something} issue is filed? |
Code Table Committee |
Add Emily Braker (needs permissions), Anna Chin (needs permissions) |
Code table permissions granted to Emily and Anna |
I also don't have code table permission. Should I have that access added or just rely on Aren to make cultural changes? |
You now have code tables permissions Angie, proceed with caution... |
Thanks. Since i don't even know how or where to go to make changes, I'm pretty safe for now... ;-) |
There's some fairly minimal documentation at http://handbook.arctosdb.org/how_to/How-to-Use-Code-Tables.html. |
Committee created and CT projct made |
We done here? Tentatively closing.... |
I propose that we add the position "Code Table Administrator" to the AWG.
It should not take two months to get parts, attributes, or other code table items added. Requests for these types of additions often go unnoticed which means that someone is not getting their data in or they are using less-than-perfect means to do so. I think it would be good to have at least three people responsible for monitoring the GitHub for these kinds of requests and assisting with getting them cleared up. We also need to make sure we have some good guidelines for such additions written in the documentation so that we don't just start adding things willy-nilly without definitions.
The text was updated successfully, but these errors were encountered: