Academic Logbooks

Log book from the HMS Dolphin, Jan. 1765.
Public domain, from Wikimedia Commons.

In a previous post, I wrote about keeping an academic portfolio to maintain current records and evidence files of academic work and output.

In this post, I want to describe another element I have added to these portfolios: logbook spreadsheets that record not just confirmed outputs, but academic effort. These spreadsheets make it easier to fill out my annual review materials, midterm / tenure / promotion dossiers, etc., and also provide possibly-useless statistics like my personal acceptance rates.

Teaching Logbook

My teaching logbook consists primarily of a sheet recording all of the classes I teach, including:

  • Term
  • Course (number and title)
  • Section (number, grad/undergrad, modality)
  • Enrollment
  • Student eval summary (instructor rating course rating)

This table can then almost be copy-pasted as-is into portfolio or dossier evidence sheets, and makes it easy to generate statistics (e.g., my department wants to see the average instructor & course ratings broken down by modality).

Research Logbook

My research logbook has two different primary log tables in it: one for submitted papers, and another for submitted proposals.

Paper Log

The paper submission log includes:

  1. Submission date
  2. Submission venue
  3. Expected publication year
  4. Submission type (journal, full conference, short, workshop, etc.)
  5. Outcome (pending, reject, accept, etc.)
  6. Publication date (for accepted work)
  7. Lead (who led this submission?)
  8. Title

I then use pivot tables to summarize submission by type and outcome, or any other statistics that seem interesting or that will support review materials I am preparing.

Proposal Log

The proposal log is similar, logging all grant submissions:

  1. Funder
  2. Program
  3. Funder Type (public / nonprofit / corporate)
  4. Submission Date
  5. Status
  6. Host Institution (where I was when I wrote the proposal, since I’ve moved institutions a few times)
  7. Lead Institution
  8. Grant start date
  9. Grant end date
  10. Grant / proposal amount
  11. Supplement amount (e.g. REU supplements on a funded grant)
  12. Total amount (grant + supplement)
  13. Local Share (portion of grant at my institution)
  14. My Share (portion of grant I get credit for)
  15. Role (PI, co-PI, Sr. Personnel, etc.)
  16. Title / Topic

This then supports counting proposals or totalling proposal amounts by type, outcome, host, etc.

COI Log

One final logbook is my “COI log”: a list of all of my collaborators with a quick project key and last-active date. This is primarily to support preparing COI lists for things like NSF proposal submissions.

It has the following columns:

  1. “Code” — the code used in the NSF COA spreadsheet (usually C or A)
  2. Name
  3. Affiliation
  4. Email
  5. Why? — reason for collab: paper, ongoing collab, preprint, workshop, permanent COI, etc.
  6. Project — short project keyword, to make it easy to filter for collabs on a particular project
  7. Last Active — the date our collaboration was last active, often empty, but used to mark end or pause of collab
  8. Last Submitted — the last date we submitted something together
  9. Last Published — the last date we published something together
  10. Timeout — compute field with the number of months since last activity / submission / publication.
  11. Active — whether the collaboration is currently active, based on reason, and whether a “Last Active” date has been set.
  12. ACM COI — whether we have a current COI by ACM’s rules, based on Active and Timeout (24 months).
  13. NSF COI — same, except with ACM’s timeout rules (48 months)

The timeout field uses the following Excel formula:

=LET(refdt, MAX([@[Last Active]], [@[Last Submitted]], [@[Last Published]]),
     IF(AND(refdt < TODAY(), refdt >= DATE(2000, 1, 1)),
        DATEDIF(refdt, TODAY(), "m"), 0))

Logging Service

These ideas can also be extended to logging service activity. I do not currently use spreadsheets for service logging, but it’s a good idea. I do log my reviewing activity in an Obsidian document, and automatically extract the review section of my CV from that task list.

Concluding Thoughts

As with saving documentation and evidence, it’s easier to summarize and report on your activity if you keep records of it as you go. A few spreadsheets can make that work, and also support personal academic analytics as well as make it easier to prepare things like NSF COA lists.