Latest Demo

---=== MP4 Video: GREN Map Demo Mar 2022 ===---

Current Progress

(As of June 2020.)

Feature Development Roadmap

  1. Publish (in progress)
  2. Polling mechanism
  3. REST endpoint security
  4. Simple data collation:
    • Set CRUD rules
    • Apply rules
    • Report on rules
  5. Entity deletion in hierarchical distributed database
  6. Levels of detail on the map, based on zoom
  7. Limit node / link query to current view bounding box
  8. Filter view based on Properties
  9. Customisable branding and colour schemes
  10. Production deployment
  11. Infinite scrolling/centring on map
  12. Add logos to input data and display in appropriate place
  13. Document recommended properties
    1. A semantically meaningful REST registry
  14. Check compliance with ‘required’ properties ("What is my data missing?")
    1. Auto register when accessing data through graph QL (to know what is missing)
    2. Check a GRENML file?
    3. Check vs registry?
  15. Allow Properties and other fields to contain formatting (Markdown?)
  16. Store data source/provenance as a property, or even field (Where did the data come from? What would this mean?)
  17. Switch back end display language with button not just browser settings
  18. Get translations for back end.
    • French
    • Portuguese
    • …
  19. Multi-language support in data and display for data
  20. Zoom to REN
  21. Set starting centre for REN
  22. Search box
  23. Call home for DB/server node version checking
  24. Custom map tiles
  25. Serve tiles from local DB node
  26. Show directly connected institutions (owners of nodes directly connected to this institution.)
  27. GRENML library error reporting / logging
  28. SSO (e.g. CAF, eduTeams)
  29. Node audit logging (who did what when?)
  30. Custom easy to use UI for backend (through API)
  31. Make entity API available
  32. Editable Map view (for creating and editing nodes, links)
  33. Draw link paths if supplied
  34. Draw curved not straight links
  35. Separate straight links to same place visually (i.e. backup/duplicate links)
  36. Show labels on map (toggle?)
  37. Add architecture / design direction to gitlab documentation
  38. Show node status information / health in back end.
  39. Select published GRENML version
    1. Revert to previous
    2. Preparation stages
  40. Improve Node / Link drawing order
  41. Improve round trip testing (this is needed)
    1. Import-export
    2. Export-import
  42. Mark data as private to prevent being published outside of owner node



  • No labels