Skip to content

keys are not unique across all files #81

@kellijohnson-NOAA

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.

Steps

  • Find how many keys are duplicated in the repository currently, maybe write this as an automated GitHub action that reports the values so they can be tracked over time.
  • Write a function to group reports together by bibdate.
  • Write a function to use biblabel to make the keys unique.
  • 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