-
Notifications
You must be signed in to change notification settings - Fork 30
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
Flag an issue: add link to support article (documentation) #378
Comments
I have the start of an article drafted on the topic - it will require some (planned) work in a testing environment to fully document the process. |
hi @timhicks-ala, is the article done so I can start to work on this issue. |
hi @nickdos, do you have any idea if the above-mentioned article is available now? |
adam-collins
pushed a commit
that referenced
this issue
Jan 30, 2024
So the "?" links to the article? Looks fine to me if so. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Based on support tickets and Twitter posts by users, there is an expectation that ALA can review and correct flagged issues, ourselves. Thus when issues remain uncorrected for months & years, it can seem like ALA is at fault.
We currently provide no information about the process of dealing with user annotations:
Provide a short sentence explaining that suggested corrections need to be corrected at the source institution and ALA cannot guarantee the institution will take action.
Add a link to a support article that provides more information about the process.
The text was updated successfully, but these errors were encountered: