excites / geokey Goto Github PK

Create a view that allows for access to all features a user has contributed to a project.

Update:

• Endpoint: `/ajax/projects/{project_id}/views/{views_id}
• Methods: PUT

Delete:

• Endpoint: `/ajax/projects/{project_id}/views/{views_id}
• Methods: DELETE

• Narrow columns, probably 6 columns are enough
• Adjust responsive breakpoints

Update

• Endpoint: `/ajax/projects/{project_id}/views/{view_id}/usergroups/{group_id}
• Methods: PUT

Add user

• Endpoint: `/ajax/projects/{project_id}/views/{view_id}/usergroups/{group_id}/users
• Methods: PUT

Delete user

• Endpoint: `/ajax/projects/{project_id}/views/{view_id}/usergroups/{group_id}/users/{user_id}
• Methods: DELETE

Endpoint: /api/project/{id}/view/{id}/features/{id}/observations
Methods: GET, PUT, DELETE

Messages should be displayed in context rather then on top of an section in the page.

API: /api/projects/{id}/views/{}
Methods: GET

• Endpoint: `/ajax/projects/{project_id}/featuretypes/{featuretype_id}/fields/{field_id}
• Methods: PUT

Seems to be some weird Django behavior

ERROR: constraint "respondsto_id_refs_id_4927788c" of relation "backend_observationcomment" does not exist

Endpoint: /api/projects/{id}/views/{id}/features/
Methods:
GET - Get a list of features
PUT - Update a feature of a view

Allow to reset the password. Links shall be found with all log in forms and when sign up fails due to an integrity error

Add lookup:

• Endpoint: /ajax/projects/{project_id}/featuretypes/{featuretype_id}/fields/{field_id}/lookups
• Methods: PUT

Update lookup:

• Endpoint: /ajax/projects/{project_id}/featuretypes/{featuretype_id}/fields/{field_id}/lookups/{lookupid}
• Methods: GET, PUT, DELETE

The key should be used in the hstore to assign tags

API: /api/projects/{id}/views
Methods: GET

Functionality that enables administrators to set a timeline with which to visualise the data in a given minisite using sliders. The administrator should be able to set the date range for which a slider will cover.

In addition, users (with the appropriate access) should be able to export any data added to a project within a specified time range

Endpoint: /api/projects/{id}/featuretypes
Methods: GET

Seems to be some weird Django behavior

ERROR: constraint "respondsto_id_refs_id_4927788c" of relation "backend_observationcomment" does not exist

Endpoint: /api/projects
Methods: GET

Endpoint: /api/projects/{id}
Methods: GET

https://github.com/djangonauts/django-hstore

Use ValidationError array

The idea is to filter data in views by feature type and the by certain attribute values. Currently there a five data types available. Simple rule definitions may look like

• TextField: contains %text%
• NumericField: lower than, greater than, inbetween
• DateTimeField: after, before, inbetween
• True/False: is True, is False
• LookupField: is one of

• Endpoint: /ajax/projects/{project_id}/featuretypes/{featuretype_id}
• Methods: PUT

Endpoint: /api/project/{id}/view/{id}/features/{id}
Methods: GET, PUT, DELETE

Endpoint: /api/project/{id}/view/{id}/features/{id}/observations/{id}
Methods: GET, PUT, DELETE