Scrape and harvest collections / sources - PROTOTYPE [P1(OCR)]

[nightsh]

Depends on #114

Harvesting collections and sources depends on the schema validation allowing groups of different types and package relationships in the data.json source files.

Proposed Spec For Implementation is located here: Specs For Implementing data.json Validation Schema for Dept of Ed

Format

• Scraping output
  • existing files (packages) go into a subdirectory called datasets
  • new subdirectories under the scraper output bucket: collections and sources
  • all the code iterating through output buckets needs to be adjusted
• Datajson transformer
  • package level:
    • collections new key - list of collection names
  • root level
    • a new @type value for collection type
      • same metadata as package, same rules, plus:
        • sources: list of sources names if type is collection
        • collections: list of collection names if type is source

Scraping rules:

• If a HTML page contains multiple datasets -> extract the page itself as a collection
• If a HTML page contains no datasets, but it has multiple links to pages that are collections -> extract the page as a source

CKAN extensions updates:

The datajson extension needs Collection / Source processing capabilities based on the data it finds in the data.json file.

Tasks:

• [x] Finish up the tech spec
• [x] Implement the scraping output changes
• [x] Implement the scraping rules for Collection / Source
• [x] Add the new items to the datajson schema we are using
• [ ] Load a datajson containing collections and sources into a harvester source and test

Acceptance criteria:

• [x] This page becomes a Source: https://ocrdata.ed.gov/StateNationalEstimations
• [x] This page becomes a Collection: https://ocrdata.ed.gov/StateNationalEstimations/Estimations_2011_12
• [ ] They are both visible in the ODP as such