The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Stephen Kitt <steve@sk2.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: ACM opens up much of its archives
Date: Thu, 26 May 2022 21:49:28 +0200	[thread overview]
Message-ID: <20220526214928.1beff099@heffalump.sk2.org> (raw)
In-Reply-To: <CAEoi9W4WJUS7eq47CRWF7f-UH3zMm9dYSnBfcanVFq12uTNmig@mail.gmail.com>

On Thu, 26 May 2022 13:13:12 -0400, Dan Cross <crossd@gmail.com> wrote:
> On Thu, May 26, 2022 at 1:09 PM Henry Mensch <henry@henare.com> wrote:
> > If you’re a **current** member of these societies then you should have
> > good access to journal content.
> 
> I believe this is true for ACM, but for IEEE not so much. You have to pay
> for a digital library membership _in addition to_ your standard membership.
> It's very annoying; IEEE is the one that really grinds my gears generally.

The ACM also has an optional DL membership (which costs as much as
professional membership on its own).

Both ACM DL and IEEE Xplore are also accessible through institutional
sign-ins using alumni accounts from a number of academic institutions, so
it’s worth giving that a shot too (for those with alumni accounts…). There’s
no guarantee of course; I have access to IEEE Xplore in this manner, but not
ACM DL (but I’m a member of the ACM, with the DL option).

Regards,

Stephen

  reply	other threads:[~2022-05-26 19:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 23:29 [TUHS] " arnold
2022-05-25 15:53 ` [TUHS] " Clem Cole
2022-05-25 16:00   ` Richard Salz
2022-05-25 16:01     ` Clem Cole
2022-05-26  1:54   ` Larry McVoy
2022-05-26 17:09   ` Henry Mensch
2022-05-26 17:13     ` Dan Cross
2022-05-26 19:49       ` Stephen Kitt [this message]
2022-05-26 20:39 [TUHS] " Douglas McIlroy
2022-05-26 20:43 ` [TUHS] " Dan Cross
2022-05-26 20:53 ` Clem Cole
2022-05-26 21:13   ` Charles H Sauer (he/him)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220526214928.1beff099@heffalump.sk2.org \
    --to=steve@sk2.org \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).