These "solabs_authorname.html" files
and "authorname.txt" files
for many solar physicists contain all their ADS
"abstracts" (meaning summaries). The parallel
"authorname.bib" files
contain the 1:1 corresponding bibtex input data. Tens of thousands of
abstracts and corrresponding bibdata for over six hundred solar
physicists (from Abbett to Zweibel) in just a few hundred megabytes!
The abstract files have the essential article specification
information including the ADS bibcode and ArXiv eprint code. I
collect these files since many years from
ADS
following my own research interests. I update them irregularly. Some
files badly mix namesakes.

The "solabs_authorname.html" files
furnish single-click article downloads. When ArXiv
contains a preprint then a clicker to download that preprint appears
after the ADS bibcode. On the next line there are two clickers to
ADS. The first gets you the article if it has direct pdf access (link
symbol "F") on ADS and, when publisher permission is required, if you
are at a site with the pertinent license or use vpn into such a site.
The second clicker opens the ADS abstract page to get you to the
website of a silly publisher that does not supply silent IP-checking
to ADS but requires an irritating extra detour along their own site,
or even a login. A link to my parallel authorname.bib file
sits at the top of each solabs_authorname.html file.

Many of the solabs_authorname.html files have been found by
Google. An (alphabetically correct) example: googling solabs_abbett gets you my latest collection of
William Abbett's ADS abstracts and
corresponding ArXiv and ADS links. In his case and for many others my
solabs_authorname file is the top Google result. Also for solabs_Asensio in the case of
Andrés Asensio Ramos
who triggered
the addition of these html versions.

My own habit is to instead use the pure-text
authorname.txt abstract
files
in my laptop for fast reading and
searching per editor. Also, grepping into these files delivers a
better hit rate than searching all abstracts at ADS because this
subset is limited to similar-interest colleagues, often with proper
exact-name specification.

If I want to read an article I open it with script
acads
using
the ADS bibcode listed in the authorname.txt abstract file for
that author (or a co-author). This script either finds the pdf in my
laptop or pulls it over from ADS by calling
getads. If
there is no pdf or pdf link on ADS, a browser window comes up instead
with the ADS abstract page for clicking on the ArXiv preprint or
publisher website (when available). Script
getads
uses
my institutional library permissions remotely, wherever I am and
without vpn. It puts the article in /tmp. When I add an author name as
optional parameter to
acads, it calls
getadsperauthor
which puts the article in a
directory for that author.

I prefer these command-line scripts because they work wherever I
happen to be and open the article on my screen without a browser
detour. For non-ADS-pdf publications with an "eprint" entry in the
authorname.txt files I use script
getastrophperauthor. I rarely bother to
download silly-publisher articles that have no ArXiv eprint.

When I decide to cite an article I copy-paste the ADS bibcode into my
manuscript, adding a brief who-and-what identifier as in:
\citetads{1991A&A...252..203R} % Rutten++ basal boundary
BibTeX then uses the parallel bibfile collection via my
bibtex script
to
generate the citation (with corresponding ADS clicker) and the
reference fully automatically, as described here. It will flag finding duplicate bibitems
("Repeated entry") for every co-author, to be ignored since they are
all the same.