Custom Query (2152 matches)

Reported by dread, 4 years ago.

• Producing daily dump file
• Publishing at ckan.net/dumps/ or better

Reported by dread, 4 years ago.

Review what chunks of code we have and how to move forward with requirements.

Requirements:

• Bulk parsing is done away from the CKAN server

Possible future requirements:

• /importer for importing spreadsheets in WUI
• validation-light - 'scoring' a package

Current importers:

• /importer controller uses: PackageImporter?, form, PackageSaver?
• loader uses: package_importer -> API
• API uses: form, PackageSaver?

Modules

• package_importer:
  • xls/csv --SpreadsheetData?--> table
  • table --DataRecords?--> records
  • records --PackageImporter?--> pkg_dicts

• pkg_dict --form--> fs & validation
• fs --PackageSaver?--> package

Reported by dread, 4 years ago.

When performing maintenance on CKAN it may be necessary to make CKAN obviously read-only, telling the users and restricting access to 'edit' pages.

Examples of use:

• Administrator wants to upgrade CKAN or move it to another server. During this time the database is being administered and either edits are lost or can't be done.
• A CKAN is used just for distributing metadata and so is always read-only. Updates may still arrive through direct db manipulation, e.g.:
  • another (but writable) CKAN instance is connected to the same db
  • restoring database dumps from another CKAN db
• Should a security be breached, all editing could be stopped