Landing pages also allow vendors to provide a consistent experience between users who have access to the item itself and users who don't. Whether that urge for consistency is warranted in any given case is a separate question, of course.
On Thu, Feb 15, 2024 at 3:25 PM Sarah Swanz <spsw...@umich.edu> wrote: > Similarly, CrossRef requires that DOIs link to landing pages and not the > content file directly. > This is their rationale: > https://www.crossref.org/documentation/member-setup/creating-a-landing-page/ > > Sarah Swanz > School of Information, MSc ’18 > University of Michigan, Ann Arbor > On Feb 15, 2024 at 2:08 PM -0600, Eric Lease Morgan < > 00000107b9c961ae-dmarc-requ...@lists.clir.org>, wrote: > > Why do we -- librarians -- point people to splash/landing pages instead > of the actual content? > > > > We digitize stuff. We describe it. We put it on the Web. And then we > point people to the descriptions instead of the real things. I understand > the need/desire to make people aware of the metadata, but the metadata does > not really give a link to the real thing. Instead, I must look over a > splash/landing page, identify the download link, and click. Such is fine > for a single one-off item, but when there are dozens (if not hundreds) of > desirable items, then I am inhibited from click/save, click/save, > click/save, etc. > > > > -- > > Eric Morgan <emor...@nd.edu> >
