-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Enhancement: allow for alternate EAD linking to digitized objects #68
Comments
ctgraham
added a commit
to ulsdevteam/islandora_solution_pack_manuscript
that referenced
this issue
Sep 7, 2021
ctgraham
added a commit
to ulsdevteam/islandora_solution_pack_manuscript
that referenced
this issue
Sep 8, 2021
ctgraham
added a commit
to ulsdevteam/islandora_solution_pack_manuscript
that referenced
this issue
Sep 10, 2021
…nsform when not needed
ctgraham
added a commit
to ulsdevteam/islandora_solution_pack_manuscript
that referenced
this issue
Oct 5, 2021
ctgraham
added a commit
to ulsdevteam/islandora_solution_pack_manuscript
that referenced
this issue
Oct 27, 2021
…logic is more complicated
ctgraham
added a commit
to ulsdevteam/islandora_solution_pack_manuscript
that referenced
this issue
Nov 2, 2021
ctgraham
added a commit
to ulsdevteam/islandora_solution_pack_manuscript
that referenced
this issue
Nov 5, 2021
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Links to digital objects from the EAD currently depend on the configuration of search keys:
https://github.com/discoverygarden/islandora_solution_pack_manuscript/blob/7.x/README.md#q-what-elements-are-necessary-in-finding-aid-ead-metadata
With the child objects' metadata referencing the box and folder.
Another possible implementation could be to use the
xlink:href
fromDAO
entries for linking within the Finding Aid display.For example, the href might point to a link resolver, a DOI, or just a URI or unique ID. An additional setting could be added for an optional prefix to apply to the xlink, e.g. "https://doi.org/" or "/islandora/object/".
The text was updated successfully, but these errors were encountered: