Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O
openalex
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 3
    • Issues 3
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • crawlers
  • openalex
  • Issues
  • #6

Closed
Open
Opened Feb 24, 2025 by Przemyslaw Kaminski@cgenie
  • Report abuse
  • New issue
Report abuse New issue

Review our API implementation and leave only what is needed for us

Initially, when writing an openalex API client, I wanted to have a complete definition, so that later, in gargantext, we have freedom to pick fields that we want.

Maybe this wasn't the best idea -- turns out some fields still can be missing in openalex (or maybe they change their API specs from time to time) and this library throws parsing errors (which are usually easy to fix, by adding a Maybe type to a key).

So let's fix this more: review what gargantext needs currently and import only these fields in this library. Ignore the rest.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: gargantext/crawlers/openalex#6