Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Records #172

Closed
12 tasks done
wonderchook opened this issue Apr 28, 2016 · 0 comments
Closed
12 tasks done

Records #172

wonderchook opened this issue Apr 28, 2016 · 0 comments
Assignees
Milestone

Comments

@wonderchook
Copy link
Contributor

wonderchook commented Apr 28, 2016

Summary

Records consists of Location, Relationships and Parties. All three of these items are closely related to each other so they are laid out below. A record must have at least one entry of a location(note: I can’t think of a way you could have a relationship without at least a location or a party). For example some location data might not contain ownership information so it may only contain parcel records in that project. Other project may contain location (showing the geometry of a parcels), relationships (showing the ownership) and the parties (information about the person or organization that owns/has rights to the property)

  • Location: geometry of a record, can be a point, line or polygon. Parcels, points of interest, community boundaries, pastoral grazing paths
  • Relationships: Links locations to parties or locations to locations. Can be relationships such as tenure.
  • Parties: organizations, people or other entities associated with a location.

Links to requirements and functional testing script

Acceptance criteria

  • User can create a new location from the map
  • User can create a new relationship and party and associate it with a location
  • User can search/sort/filter all locations in a locations view
  • User can search/sort/filter all parties in a parties views
  • User can search/sort/filter all relationships in a relationship view
  • User can delete a single location, relationship and party
  • It is not possible for a user to create orphaned relationships that are not associated with a location or party
  • User can edit locations, relationships and parties
  • User can edit geometry of locations
  • When creating and editing locations the user can see the surrounding parcels

Task list (including tests)

Spatial unit data modelling and API work split out as #177

  • Data modeling (including managers if needed and integrity checks) (except spatial units)
  • API design (except spatial units)
  • API documentation (except spatial units)
  • API Review (except spatial units)
  • API Views/Serializers Parties
  • TEST Parties API (create, view, update, delete)
  • API Views/Serializers Relationships
  • TEST Relationship API (create, view, update, delete)
  • UI Add new record workflow
  • UI Edit view location including deleting
  • UI Edit view parties including deleting
  • UI Edit views relationship including deleting
@wonderchook wonderchook added this to the Version 0.1 milestone Apr 29, 2016
@linzjax linzjax self-assigned this May 2, 2016
@linzjax linzjax removed their assignment Jun 3, 2016
@oliverroick oliverroick self-assigned this Jun 10, 2016
@seav seav closed this as completed Jun 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants