Comment 3 for bug 1261939

From IRC earlier today:

[09:27:14] <bshum> dbs: bug 1261939 was entertaining. Took me a few moments to figure out that the example.com external URL was being used instead of the hostname/eg/opac/library/shortname path I was initially expecting to get me to a given library page.
[09:27:16] <pinesol_green> Launchpad bug 1261939 in Evergreen "Add per-library TPAC pages with schema.org structured data support" (affected: 1, heat: 6) [Wishlist,New] https://launchpad.net/bugs/1261939
[09:28:35] <bshum> I'm not entirely sure I like that, but we don't get external URLs in our system for org units (yet). So I'm unsure how we'd implement it down the road.
[09:35:25] <dbs> Yes, MassLNC wanted the OUS for a URL to an external library page; the built-in pages just get dropped into place if there's no OUS
[09:35:49] <dbs> Good to expose that OUS via sample data so that people are aware that it exists I guess :)
[09:36:07] <bshum> Hehe
[09:37:36] <bshum> I guess it's just my personal opinion that if we create catalog library pages, I'd like to keep us within the catalog primarily and then have those links out to external library pages based on the OUS at the point you see it on the library info page.
[09:37:49] <bshum> Rather than link straight to the external URLs
[09:37:56] <bshum> But then, I don't use the feature.
[09:38:18] <bshum> So I don't really know.
[09:39:13] <dbs> bshum: sure, we could check with MassLNC to see if that would work for them
[09:39:43] <dbs> I suspect that if they had the built-in library pages to start with, then they might have opted for that design too
[09:40:02] <kmlussier> What exactly is it that you want? The library names to link to the library page which would then link to the external URL?
[09:40:37] <dbs> kmlussier: that's what bshum is suggesting, yes... so that you don't get thrown out of the context of the catalogue when you're just browsing copies
[09:40:52] <dbs> (or at least that's what I think he's saying)
[09:41:09] <kmlussier> Yes, we came up with that idea before there were library pages to link to, but I would need to check with people here to see what they think.

I just checked with my team here. I don't think we would object to it pointing to the library page by default, but we also think there are some sites that will prefer the link to the external web site. I don't think it needs to be a OUS, though. Maybe a setting in config.tt2 or even just a comment in the tt2 file letting people know how to customize the page to link to the external URL?

Also, is there any chance we could change the default label from External web site to Library web site? I know we can customize the language, but I was thinking "Library web site" would be a more user friendly label to use out of the box.

Thanks Dan! I love the page and think patrons will find it very useful!