Skip to content

Data publishing for data from third-parties that don't allow data sharing #33

@tkuhn

Description

@tkuhn

How should we deal with studies that use data from third parties like Twitter that don't allow for data sharing? According to the PLOS guidelines (http://journals.plos.org/plosone/s/data-availability), which we are following for now, it seems that such studies couldn't be published (though there are recent PLOS One articles on Twitter studies...). The publication of aggregated, post-processed data (e.g. data points in a plot) should always be possible though. So it seems we have the following options:

  1. Allow exceptions to data availability requirements for cases of third-party data with terms of service that don't allow for data sharing
  2. Interpret data availability requirements in a loose way that is compliant with just releasing aggregated post-processed data (e.g. data points in a plot)
  3. Don't allow for exceptions and apply data requirements in a strict way: We won't be able to publish Twitter studies in this case
  4. Are there other options?

Which one should we follow? I am undecided...

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