Skip to content
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

As a content editor, I want to see other documents on the same fragment as part of a document detail view in order to ensure I'm not creating a duplicate description. #653

Closed
4 tasks done
richmanrachel opened this issue Feb 24, 2022 · 3 comments
Assignees

Comments

@richmanrachel
Copy link

richmanrachel commented Feb 24, 2022

testing notes

  • on admin document edit form, you should see a section for "other documents on this fragment" only if there are other documents linked to any of the same shelfmarks
  • should display pgpid, title (type + shelfmark), and description
  • should link to the admin edit page for the document
  • should not see the section or links if there are no other documents on the same fragments

Per Alan's request in Slack, User-Story-Sandbox message 2-21-22.

Perhaps we can use the Related Fragments section to also capture documents with the same fragment/shelfmark but different PGPID.

I think we'll need: shelfmark, pgpid, document description, type, and some indicator to show how we're using this differently than matching a join.

dev notes

adapt public site related documents logic; add description; display above image/transcription on document change form

@richmanrachel
Copy link
Author

Realizing that this intersects with #716

Would it make sense to distinguish "Related Fragments" (which captures joins and potential joins, and should mostly live on the admin site to facilitate joins) from "Documents on the Same Fragment" (which would show the description and link to other PGPIDs with the same shelfmark and should exist on both frontend and admin site)?

@richmanrachel
Copy link
Author

We also have #556 to display Related Fragments on frontend.

Not sure about the best solution, but @rlskoeser I'll flag these for discussion when you get back.

@rlskoeser rlskoeser self-assigned this Jun 9, 2022
@rlskoeser rlskoeser added the 🗜️ awaiting testing Implemented and ready to be tested label Jun 9, 2022
@richmanrachel
Copy link
Author

@rlskoeser - this is fantastic! So excited about this feature :D

@richmanrachel richmanrachel removed the 🗜️ awaiting testing Implemented and ready to be tested label Jun 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants