Text for broken link message

[varnum]

Use what's on ArticlesPlus for problem reporting (bold text is link):

Full text link not working? Please let us know.

[jonearley]

Full text link not working? Please let us know.

I'd argue this is worse online copy and introduces inconsistent naming in MGet It. We don't refer to anything as full text links. As of now we use "online access [links]" in the not available copy which is more generic for accommodating items like videos or images.

Found a problem? [Let our team of link fixers know]().

The report a broken link message is in context (just below) the set of links giving proximity reference to what you're reporting a problem on. It might be redundant to reference the links.

Found a problem

Is easy to understand and has high readability

[Let our team of link fixers know]().

Friendlier and less typical copy than "please let us know".

@bnhowell What do you think of the UX here?

I might be splitting hairs, but I think online copy is where UX effort is worth some time.

[varnum]

The discussion was around the distinction between reporting a broken "Get Item" / "Go to BLAH" link (bottom of link section) -- filling in a form and not getting an immediate response -- and getting help with research (right column) -- getting live help [during business hours]. The wording needs to make those distinctions.

Ken Varnum Senior Program Manager for Discovery, Delivery, and Library Analytics Library Information Technology | University of Michigan Library varnum@umich.edu | @varnum | 734-615-3287 http://www.lib.umich.edu/users/varnum

On Wed, Aug 10, 2016 at 2:56 PM, Jon Earley notifications@github.com wrote:

Full text link not working? Please let us know http://url.

I'd argue this is worse online copy and introduces inconsistent naming in MGet It. We don't refer to anything as full text links. As of now we use "online access [links]" in the not available copy which is more generic for accommodating items like videos or images.

Found a problem? Let our team of link fixers know.

The report a broken link message is in context (just below) the set of links giving proximity reference to what you're reporting a problem on. It might be redundant to reference the links.

Found a problem

Is easy to understand and has high readability

Let our team of link fixers know.

Friendlier and less typical copy than "please let us know".

@bnhowell https://github.com/bnhowell What do you think of the UX here?

[image: screenshot-earleyj www lib umich edu 2016-08-10 14-54-41] https://cloud.githubusercontent.com/assets/1678665/17566707/7e868704-5f0a-11e6-9f11-1749233d585a.png

[image: screenshot-earleyj www lib umich edu 2016-08-10 14-53-39] https://cloud.githubusercontent.com/assets/1678665/17566709/801b8c04-5f0a-11e6-86a2-2882324d97ab.png

I might be splitting hairs, but I think online copy is where UX effort is worth some time.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mlibrary/mgetit/issues/17#issuecomment-238967768, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ7bL-FFqAfX6cP0MTrrDhiiuk9EfmqNks5qeh7igaJpZM4Jhbkh .

[varnum]

The undergrad, graduate, and university staff and faculty I tested regularly gravitated to a single link labelled "report a problem" that was found in the Get Help section on the right (under Ask a Librarian).

Placement issues or copy issues are good opportunities for refinement through A/B testing and analytics after launch. I don't have data at this point for what's going to work best at this time for those variables.

Proximity and context is good (The Report a Problem Link under the 'Get Item' Link/options) but... We want that section to be as direct and uncluttered as possible to minimize choices/cognitive strain/disctraction.

On Wed, Aug 10, 2016 at 3:00 PM, Ken Varnum varnum@umich.edu wrote:

The discussion was around the distinction between reporting a broken "Get Item" / "Go to BLAH" link (bottom of link section) -- filling in a form and not getting an immediate response -- and getting help with research (right column) -- getting live help [during business hours]. The wording needs to make those distinctions.

Ken Varnum Senior Program Manager for Discovery, Delivery, and Library Analytics Library Information Technology | University of Michigan Library varnum@umich.edu | @varnum | 734-615-3287 http://www.lib.umich.edu/users/varnum

On Wed, Aug 10, 2016 at 2:56 PM, Jon Earley notifications@github.com wrote:

Full text link not working? Please let us know http://url.

I'd argue this is worse online copy and introduces inconsistent naming in MGet It. We don't refer to anything as full text links. As of now we use "online access [links]" in the not available copy which is more generic for accommodating items like videos or images.

Found a problem? Let our team of link fixers know.

The report a broken link message is in context (just below) the set of links giving proximity reference to what you're reporting a problem on. It might be redundant to reference the links.

Found a problem

Is easy to understand and has high readability

Let our team of link fixers know.

Friendlier and less typical copy than "please let us know".

@bnhowell https://github.com/bnhowell What do you think of the UX here?

[image: screenshot-earleyj www lib umich edu 2016-08-10 14-54-41] https://cloud.githubusercontent.com/assets/1678665/17566707/7e868704-5f0a-11e6-9f11-1749233d585a.png

[image: screenshot-earleyj www lib umich edu 2016-08-10 14-53-39] https://cloud.githubusercontent.com/assets/1678665/17566709/801b8c04-5f0a-11e6-86a2-2882324d97ab.png

I might be splitting hairs, but I think online copy is where UX effort is worth some time.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mlibrary/mgetit/issues/17#issuecomment-238967768, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ7bL-FFqAfX6cP0MTrrDhiiuk9EfmqNks5qeh7igaJpZM4Jhbkh .

Ben Howell | Accessibility & User Experience Specialist Design & Discovery | LIT | University of Michigan Library bnhowell@gmail.com

[jonearley]

Found a problem? Let our team of link fixers know.

I went out and tested this language with two students in the library and asked them what they would do if they had a problem with a link. They then pointed out the found a problem? area. I asked what would you expect to happen if you proceeded to click the link. They said they would expect some sort of brief form to report a broken link to the appropriate staff so it could be fixed/reviewed.

[bnhowell]

Thank Jon!

+1 for copy with clarity and a business casual tone.

On Thu, Aug 11, 2016 at 12:12 PM, Jon Earley notifications@github.com wrote:

Found a problem? Let our team of link fixers know http://url.

I went out and tested this language with two students in the library and asked them what they would do if they had a problem with a link. They then pointed out the found a problem? area. I asked what would you expect to happen if you proceeded to click the link. They said they would expect some sort of brief form to report a broken link to the appropriate staff so it could be fixed/reviewed.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mlibrary/mgetit/issues/17#issuecomment-239210180, or mute the thread https://github.com/notifications/unsubscribe-auth/AQBqvyX2wA1UM7LEqk_W4ZLnpo-9r1Dpks5qe0n9gaJpZM4Jhbkh .

Ben Howell | Accessibility & User Experience Specialist Design & Discovery | LIT | University of Michigan Library bnhowell@gmail.com

[jonearley]

Since this issue was discussed and has support I'm going to close it for now. Feel free to reopen.