Make Europeana fetch viable · Issue #224 · creativecommons/quantifying · GitHub
Skip to content

Make Europeana fetch viable #224

Open

Description

@TimidRobot

Problem

The Europeana data set is too big to fetch all at once, or in its entirety.

  • data providers: 4206
  • rights: 64

Assuming approximately 1 second per query, the expected duration is approximately 75 hours.

Description

  1. Add counts for rights only (not including data providers)
  2. Write a query plan on first run per quarter to map out which queries to make over 30 runs (30 days)

Alternatives

Parallel queries (probably considered impolite, Timid Robot will ask)

Additional context

Implementation

  • I would be interested in implementing this feature.

Activity

  1. moved this from Triage to Backlog in TimidRoboton Nov 1, 2025
  2. oree-xx commented on Nov 3, 2025

    @oree-xx
    Contributor

    @TimidRobot This is interesting to see that Europeana has a lot of data providers.
    But why is the status of the issue blocked?
    Are you trying to identify or investigate something?

  3. TimidRobot commented on Nov 3, 2025

    @TimidRobot
    MemberAuthor

    @TimidRobot This is interesting to see that Europeana has a lot of data providers. But why is the status of the issue blocked? Are you trying to identify or investigate something?

    Yes

    Parallel queries (probably considered impolite, Timid Robot will ask)

  4. oree-xx commented on Nov 5, 2025

    @oree-xx
    Contributor

    @TimidRobot Is there a verdict yet on whether parallel queries can be considered?

  5. TimidRobot commented on Nov 5, 2025

    @TimidRobot
    MemberAuthor

    @TimidRobot Is there a verdict yet on whether parallel queries can be considered?

    This issue will be updated when there is more information.

  6. TimidRobot commented on Mar 6, 2026

    @TimidRobot
    MemberAuthor

    TODO:

    1. Contact Europeana to either:
      • allow parallel API queries for authenticated account (allow parallel queries)
      • update API to provide totals (so fewer queries are required)
    2. Update script, as necessary
    3. Rename script and make it executable
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

    ✨ goal: improvementImprovement to an existing feature💻 aspect: codeConcerns the software code in the repository🔒 staff onlyRestricted to CC staff members🚧 status: blockedBlocked & therefore, not ready for work🟩 priority: lowLow priority and doesn't need to be rushed

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions