Skip to content

keys are not unique across all files #81

Description

@kellijohnson-NOAA

A function or process for creating unique keys across files is needed. I am inclined to do this for just a user-defined set of files rather than across all files within journals because there are so many files. I think it would be important to sort the articles present chronologically by bibdate so if/when the grouped file is updated the old keys would not change, i.e., if "happy:2006:ABCa" and "happy:2006:ABCb" are already in the file, then a new addition would become "happy:2006:ABCc". This would not alleviate pains if a new journal was added to a grouped file. We could export information about all the names that changed though.

If the journal abbreviation is added to the key they are all unique. The new problem lies in that when a note to another article appears in one decade and the article is from a different decade then the said article is copied into the other bib file so it is listed two times that way it can be referenced in the note. This causes duplicate keys, exactly two times for 104 entries as of 2026-08-13.

Steps

  • Write a function to group reports together by bibdate.
  • Make the keys unique by adding the journal abbreviation.
  • Use this function for {asar}.

FYI

@Schiano-NOAA @sbreitbart-NOAA

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions