{"id":1615,"date":"2020-04-03T23:45:00","date_gmt":"2020-04-03T21:45:00","guid":{"rendered":"https:\/\/www.neovita.com\/thoughts\/?p=1615"},"modified":"2020-04-13T03:39:36","modified_gmt":"2020-04-13T01:39:36","slug":"writing-for-digital-products-springer-nature","status":"publish","type":"post","link":"https:\/\/www.oninteractions.com\/thoughts\/writing-for-digital-products-springer-nature\/","title":{"rendered":"Writing for digital\u00a0products: Springer\u00a0Nature"},"content":{"rendered":"\n

We should only use difficult words, because librarians are experts.<\/p>\n\n\n\n

Low effort words<\/h2>\n\n\n\n

One of my sayings is that \u201cno-one ever reads anything on the web\u201d. I\u2019ve paraphrased that from Jakob Nielsen, who already in 1997 wrote<\/a>:<\/p>\n\n\n\n

\u201cPeople rarely read Web pages word by word; instead, they scan the page, picking out individual words and sentences.\u201d<\/p><\/blockquote>\n\n\n\n

This means that the words in our tools for librarians are of no value, and essential, at the same time.<\/p>\n\n\n\n

A goal of my work is that librarians should use as little effort as possible<\/a> when they use our tools.<\/p>\n\n\n\n

I am therefore faced with quite a quandary since one of the things I do is to choose most of the words that librarians see in the Librarian Portal<\/a>: The tools need words for librarians to be able to use them, but the words need to be scannable with very low effort. How might I choose low effort words? Design methods<\/a> to the rescue: As a designer I include those who I serve in the creation of the solution.<\/p>\n\n\n\n

Usage data downloads<\/h2>\n\n\n\n

COUNTER usage data<\/a> is used to understand how patrons (students, researchers, colleagues) use licensed content on publisher platforms like SpringerLink and nature.com.<\/p>\n\n\n\n

Usage analysis librarians need to choose which set of data to download based on their current analysis needs. We have a form in the Librarian Portal to get for example \u201cthe number of PDF downloads, by journal, that my patrons did on SpringerLink last month\u201d.<\/p>\n\n\n\n

Which options the form contain is decided by the COUNTER 5 code of practice<\/a>. But how those options are shown on the page \u2013 and the words to use \u2013 is not specified.<\/p>\n\n\n\n

Experts<\/h2>\n\n\n\n

So, I reached out to six usage analysis librarians. We spoke about different types of words we might use. One choice was to use words based on the types of analysis\u2019 the librarian does with the data. An other option was to help librarians learn to use the COUNTER data by clearly explaining what each option means. A third was to just use the words that are used in the code of practice.<\/p>\n\n\n\n

The result was very clear: We should always use exactly the words that are used in the code of practice. We should not dumb down the interface, and we should not try to predict how librarians will use the data. Just use the COUNTER words. That will be most scannable and thus lowest effort.<\/p>\n\n\n\n

Therefore, the form in the Librarian Portal use words like \u201cstandard view\u201d, \u201creporting period\u201d, and \u201cmaster report\u201d. Hard core, expert words. That\u2019s awesome for our usage analysis librarians. \u2018Cause they\u2019re experts.<\/p>\n","protected":false},"excerpt":{"rendered":"

We should only use the COUNTER words, because librarians are experts.<\/p>\n","protected":false},"author":1,"featured_media":1624,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[41,22,11],"tags":[],"series":[40],"class_list":["post-1615","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-content-strategy","category-language","category-misfits","series-skills"],"acf":[],"jetpack_featured_media_url":"https:\/\/www.oninteractions.com\/thoughts\/wp\/wp-content\/uploads\/2020\/04\/writing-for-digital-products.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/posts\/1615","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/comments?post=1615"}],"version-history":[{"count":19,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/posts\/1615\/revisions"}],"predecessor-version":[{"id":1638,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/posts\/1615\/revisions\/1638"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/media\/1624"}],"wp:attachment":[{"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/media?parent=1615"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/categories?post=1615"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/tags?post=1615"},{"taxonomy":"series","embeddable":true,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/series?post=1615"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}