Skip to content
This repository was archived by the owner on Aug 25, 2026. It is now read-only.
This repository was archived by the owner on Aug 25, 2026. It is now read-only.

Dates covered vs dates collected #4

Open

Description

@ruebot

Should we make a distinction between the two in the metadata?

Activity

  1. edsu commented on Dec 30, 2016

    @edsu
    Member

    In b73897d I added an added dataset field to indicate when the dataset was added to the catalog, which is different from the date the dataset was published.

    But it sounds like you are talking about a different kind of date distinction. Are you thinking of a situation where the time period in which data collection ran does not match the time period of the tweets collected? I think this can only happen when running searches right?

  2. ruebot commented on Dec 30, 2016

    @ruebot
    MemberAuthor

    Are you thinking of a situation where the time period in which data collection ran does not match the time period of the tweets collected? I think this can only happen when running searches right?

    Exactly!

    In the Scholars Portal Dataverse, where I put our datasets, we have the option of adding date ranges for "date covered" and "dates collected". This works well for all the major collections I've done with twarc, since I use a strategy of filter and search, and then deduplication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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