-
Notifications
You must be signed in to change notification settings - Fork 1
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
include archive logo, address and contact link in finding aid viewer and archive browse #56
Comments
Could you add a link to the data I should use to populate this? Do we have a list of addresses, a link, and link text for each archive? |
Just sent the sheet to you -- also on Box -- with repo name and link. Need to copy over the addresses and supply link text for you. Wait on this -- I'll let you know when it's complete. |
Ok. I'm going to tag this as "data" for the time being- please let me know when it's ready. |
Please confirm if this is https://uchicago.box.com/s/m26ngaznoxkl9skcfl6b45uz940x8rtx. (And please still let me know when it's ready for me to ingest.) |
Ready!
…On Wed, Oct 27, 2021, 8:34 AM John Jung ***@***.***> wrote:
Please confirm if this is
https://uchicago.box.com/s/m26ngaznoxkl9skcfl6b45uz940x8rtx. (And please
still let me know when it's ready for me to ingest.)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA263WVVDZD4BA5RYHU4PWDUI75XHANCNFSM5GPBOX4A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Based on the data, there are two different ways we can proceed here. Option A is to allow site editors to be able to put whatever HTML they'd like into the archive info box. They will be able to enter information into the olive-colored rectangle in a free-form way, and that information doesn't necessarily have to include a mailing address and a link to the archive. The advantage of option A is that it will allow people to easily include things like email addresses, or link text that is part of a larger paragraph about research at that archive, or anything else they can think of. Option B is to put restrictions on the data, so a mailing address must look like a mailing address, and an email address must look like an email address. Links to each archive could become more regular too. Rather than specifying custom text for links in each case, each archive's link text will be produced automatically- but it would be a more generic message, like "Visit ." I tend to like option B because it makes the interface nice and clean, however, the data currently includes idiosyncrasies that would be lost of we did this. If we go with option A, then editors can (and probably will) put all kinds of information into that box. Which option do you prefer? |
I vote for Option A, with a caveat that I will produce content guidelines for the site. The flexibility is important. AND--generic links like "Visit" have known accessibility issues. To explain my idiosyncratic link text approach: |
Ok, that's great. And agreed about generic links like "Visit." Next, I see that there are some differences between the names of archives that we're currently using on the site, and the way those archive names appear in the spec. Here are a few examples, spec first, current site second: Spertus Institute, Library and Collections Chicago Youth Centers CPL-Vivian G. Harsh Research Collection, Woodson Regional Which set of archive names should I use? Should I use the set in repoLinks.xlsx, or the ones that are currently on bmrcportal-test? |
I'm guessing the ones in repoLinks but I'll double check.
…On Thu, Oct 28, 2021, 12:08 PM John Jung ***@***.***> wrote:
Ok, that's great. And agreed about generic links like "Visit."
Next, I see that there are some differences between the names of archives
that we're currently using on the site, and the way those archive names
appear in the spec
<https://uchicago.box.com/s/m26ngaznoxkl9skcfl6b45uz940x8rtx>. Here are a
few examples, spec first, current site second:
Spertus Institute, Library and Collections
vs:
Spertus Institute, Library & Collections
Chicago Youth Centers
vs:
Chicago Youth Centers (CYC)
CPL-Vivian G. Harsh Research Collection, Woodson Regional
vs:
CPL-Vivian G. Harsh Research Collection
Which set of archive names should I use? Should I use the set in
repoLinks.xlsx, or the ones that are currently on bmrcportal-test?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA263WWPSIAMRMUT5MO5GKDUJF7RFANCNFSM5GPBOX4A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Also, please provide a link to a folder containing the logos for each repository when you can. |
some may be missing; I'll have the student worker take a look next week. |
Spertus uses the ampersand. |
This information should also appear in the sidebar of the finding aid viewer- see this mockup. |
This is now implemented in b941c76 and live on the server. Please take a look when you have a chance- there are still some archives missing logos, so if you'd like me to keep this open and tag it as "data" just let me know. Also, please note: adding repository information to the finding aid viewer sidebar increased the width of the sidebar in lots of cases. I'm going to deal with that issue in #51. |
Yes, do keep open as "data" -- I'll ask Warren to check on that this afternoon after 1pm. |
In issue #51 I'll probably constrain the width of the logo to about 60% of the width of the sidebar to get it to match the mockup, and I'll figure out something appropriate for mobile too. Some of the logos are relatively low resolution- you might want to get higher-resolution versions to keep them from upsampling. |
This looks good!👌 |
Can you kindly take note of the ones that are lo-res? We'll ask the
institutions for better ones.
…On Fri, Nov 5, 2021 at 10:51 AM John Jung ***@***.***> wrote:
In issue #51 <#51> I'll
probably constrain the width of the logo to about 60% of the width of the
sidebar to get it to match the mockup
<https://uchicago.app.box.com/file/807084219878?s=86ze2stummldz0bma0ek278dl9k7nphr>,
and I'll figure out something appropriate for mobile too. Some of the logos
are relatively low resolution- you might want to get higher-resolution
versions to keep them from upsampling.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA263WQNEB2JPNZY23UMH3DUKQDRTANCNFSM5GPBOX4A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
To demonstrate, choose Browse Archives from the home page. Select an archives, for example, the Harsh. The selected facet appears at the top of a results list for all collections from that archives.
Here is the mockup version of the page: https://uchicago.box.com/s/1laay3kuo5q9vdo6olbyid0991hyahea
At the top of the results list is a banner or content box going across with information about the repository -- this is a nice feature! the information and design appear in a smaller version in the sidebar of a finding aid.
The text was updated successfully, but these errors were encountered: