-
-
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
Better Project metadata for querying and curation #2570
Comments
Seems reasonable.
I have NO idea how this is related. CollectionA gets a loan request, makes a project, eventually CollectionZ sends the same person samples for the same reasons, they should just use the same project. CollectionZ's stats depend on usage, not who created the project.
Count the linked data? If there are none, the project does nothing anyway (and I'll eventually argue for automated deletion of those - I can use created data too!) Ugh... |
Suggest adding "project created by" to project agents |
"project created by" |
NOT metadata pulled from environment; these will be new values in http://arctos.database.museum/info/ctDocumentation.cfm?table=CTPROJECT_AGENT_ROLE |
from #2541 (comment) AWG suggestion
|
Documentation: discourage HTML in project title. |
todo:
|
I suggest we give everyone a time frame for padding them intentionally, after which we add some text that purposefully pads them in a way that lets us find them:
Adds greater than 100 characters to any project description. |
Agree with adding required text.
…On Thu, Apr 2, 2020 at 1:31 PM Teresa Mayfield-Meyer < ***@***.***> wrote:
* UNM-IT Warning:* This message was sent from outside of the LoboMail
system. Do not click on links or open attachments unless you are sure the
content is safe. (2.3)
these MUST be padded out before implementing rule
I suggest we give everyone a time frame for padding them intentionally,
after which we add some text that purposefully pads them in a way that lets
us find them:
This project was created with a description that included less than 100
characters. To remove this text, increase the project description to
greater than 100 characters.
Adds greater than 100 characters to any project description.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2570 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADQ7JBEP6SBMHMFJTROICFDRKTR2BANCNFSM4LWWFP7A>
.
|
Here's a list of projects with a short description and/or no associated transactions. "Tooshort" projects will be subject to #2570 (comment). "Doesnothing" projects will be discussed later; DLM recommends automatic deletion after some reasonable period of time (2 years???). code
|
Add to search: uses stuff from institution |
AWG says go |
Entered/edited in next release. |
Right now we have no way of knowing who created or last edited a Project, which is important for a variety of reasons. One is end of year reporting on collection activity.
I would even like to have some indicator of the primary collection a Project is associated with (e.g., MVZ Birds, MSB Mamm, etc) This could be included in the title of course as a best practice (e.g., we start project titles with "MVZ Archives:" ) but that is cumbersome, denormalizing and frustrating.
We should discuss if we need other curatorial controls on who can edit as well such as toggles like on locality (accepted, verified)
Once decisions are made on how, this would allow searches on Projects to be narrowed or filterd on collections which would facilitate queries.
Related to #2567
The text was updated successfully, but these errors were encountered: