Skip to content
This repository was archived by the owner on May 29, 2018. It is now read-only.
This repository was archived by the owner on May 29, 2018. It is now read-only.

Classifying software citations #2

@bmcfee

Description

@bmcfee

The mapping between paper text/citations and software projects will probably be difficult. Here are a few ways I see this going down:

  • Direct citation of software with a proper DOI. This our best case.
  • Citation/footnote of software via url. This is probably more common (depending on field), but also not hard to catch.
  • Citation of a paper related to a project. Some software authors prefer this method, since it maps directly onto their h-index. Downside: these look just like ordinary paper citations. We'll probably need a preliminary web crawl of projects in this category before analyzing paper text.

What else can go wrong? Have other previous studies run into and/or solved these issues already?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions