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

Add ADR and comments for resource-per-collection decision #743

Merged
merged 1 commit into from
Feb 28, 2020

Conversation

hackartisan
Copy link
Member

closes #719

@@ -0,0 +1,35 @@
# 5. N IIIFResources per N Collections it's a member of
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good, but I found this title confusing. Maybe "Create a IIIFResource for each Collection that a resource is a member of"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 done

closes #719

Co-authored-by: Trey Pendragon <tpendragon@princeton.edu>
@coveralls
Copy link

coveralls commented Feb 28, 2020

Coverage Status

Coverage remained the same at 100.0% when pulling fc59fd7 on 719-resource-adr into 6ca2095 on master.

@escowles escowles merged commit 977c59b into master Feb 28, 2020
@escowles escowles deleted the 719-resource-adr branch February 28, 2020 16:56
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

Successfully merging this pull request may close these issues.

Generate ADR about the decision to have 1 IIIF Resource per Figgy Resource per collection it's a member of.
3 participants