Skip to content

Reintegrate ckanext-spatial upstream into catalog.data.gov #3938

Description

@btylerburton

User Story

In order to reduce our maintenance burden, Data.gov team wants investigate whether we can reintegrate catalog.data.gov with the upstream version of the ckanext-spatial extension.

Reference:

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

  • GIVEN [a contextual precondition]
    [AND optionally another precondition]
    WHEN [a triggering event] happens
    THEN [a verifiable outcome]
    [AND optionally another verifiable outcome]

Background

[Any helpful contextual notes or links to artifacts/evidence, if needed]

Security Considerations (required)

[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

Sketch

  • Check if catalog builds and functions correctly with ckanext-spatial upstream.
    • Reintegrate with upstream.

Metadata

Metadata

Labels

CatalogRelated to catalog component playbooks/roles

Type

No type

Projects

Status
🗄 Closed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions