rfc/draft: mass-contribution page

[l4u532]

Problem Statement

The greater OpenBeta's route database, the more valuable it becomes to its users. OpenBeta currently falls short of substantial route data for example for Europe. To grow the database, I propose a streamlined process for bulk contributions of area, crag and route data.

Proposed Solution

• Create a separate, specific page for mass contributions where users can bulk-upload JSON data
• Have the frontend call database mutations

Preventing Misuse and Data Quality Problems

• In the beginning, restrict usage to users with explicitly assigned role
• Provide user with JSON templates
• Validate data in the frontend before submitting
• Allow for max 1,000 entities (i.e. crags/areas/routes and a max of 3 MB filesize)

Mockup

How important is this to you (Please pick one)

• Critical

[isaac-aa]

I love this idea! Regarding the JSON template, rather than a template, proper documentation could be written, such that all details (units, defaults, optional stuff,...) are correctly specified.

[Silthus]

Great idea!

I think providing a Json template for download (in addition to documentation) offers the benefit, that users can simply download the file and adjust the values in it, then re-upload.

With just docs it would require substantially more work to get started.

---

In addition it would be great to add a new field to the database accepting arbitrary Json data and storing it. Retievable through the api only. This would allow for a lot more flexibility when bulk adding new areas and climbs that have more metadata than what is supported by the DB.

[l4u532]

update: working on finalising the frontend. what's there already:

• json schema validation
• dynamic gql query creation (using mutation bulkImportAreas)
• user guide