Skip to content
This repository was archived by the owner on Nov 10, 2017. It is now read-only.
This repository was archived by the owner on Nov 10, 2017. It is now read-only.

Fix the reference_v30_value / reference_vs30_value name consistency issue #30

@larsbutler

Description

@larsbutler

There is a mismatch in this value between the client and most of our backend code. We're having to deal with 'translating' this value (for example, in geonode.mtapi.views.prepare_job()).

We need to implement a permanent solution (fix the inconsistent naming) and remove these translation workarounds.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions