erikpl / sdg-ontology-visualizer Goto Github PK

• Send api call on scrolling

• Languages dropdown with prioritizing
• Check what languages the UI is translated in

• Remove sub-sub-sub-sections in the architecture section?
• Rewrite parts of the report to avoid using the words "we" and "our"
• Consider merging the preliminary research and product sections
• Add "architectural patterns" section
• Create new deployment diagram
• New architecture section introduction
• Write about the process view
• Write about the logical view
• Write about the deployment view
• Write about the implementation view
• Write about the use cases
• Add supervisor name to front page
• Changes to the introduction (common thread, citation, stakeholders etc.)
• Add explanation of Pizza tutorial to section 2.2
• Add sources to section 2.4 (and rewrite some descriptions)
• Make sure Figure 2 (section 2.4) is referred to in the text
• Restructure the competencies section
• Work on the product chapter (especially with the architecture)
• Make summary table for requirements
• Testing (more about user testing and write about automated tests)
• Refer to project plan image in 4.1.1
• Figure 7: We have to make our own instead of using what a previous group have made
• Remove or move figure 11
• Add overview of work distribution (4.4.1)
• Refer to Corona as either "Covid-19" or "Corona" with the same name in the whole report (be consistent)

• Eskild
• Erik
• Olga

• Create query function to retrieve policy documents for a target

• Create query execution function to retrieve policy documents for a target

• Add necessary logic and routes

Deler som må skrives:

• Project overview
• Product development
• Further work
• Customer and supervisor collaboration
• Development tools and standards
• Sprint diary Storsalen
• Sprint diary Knaus
• Sprint diary Bodegaen
• Summary

Change from rdf to SDG

// Insert use-cases later, the ones we find most useful to understand.

https://trello.com/b/SjP68HUc/sdg-icons-in-languages

• Expand introduction
• Remove/explain future developers as stakeholders
• Expand on required competencies
• Fix subject-object example in RDF section
• Picture of existing solution
• Risk matrices

• Thea
• Sebastian

TODO: insert a more specific description of the issue (at hand).

• Eskild
• Olga

• Snapshots for new components
• Update existing tests to account for code changes
• Integration test that covers new all new functionality

• Type of documents filter
• Active/inactive filter
• Search field

• Targets don't appear in the graph because they're filtered away by one of the 230982 filters in the backend
• Graph won't update when language is changed
• State isn't retained on page refresh
• Language tags are invisible on drag

(I don't think we have the time to address all of these)

• Convert JSON files to OWL entries, relations etc.
• Put the stuff in the database

Some ontology ideas:

3 classes:

• PolicyDocument (many individuals)
• Language (individuals are the 23 languages)
• Format (individuals are the 3 formats)

Properties:

• Subgoal has PolicyDocument, documents (individuals) have a subgoal?
• PolicyDocument has Language, Format

Example (not complete or anything, just an outline):

Only conceptually, to help us move on. We should expand the 4+1 diagrams to fit in the first feature (SDG policies).

• Process (+ HTTP requests to get policies)
• Physical (no changes)
• Use case view (+ new case where a user wants to find policy documents)
• Also maybe make a sequence diagram, just to see how we should implement the "flow"

• Get the documents from the server
• Display them nicely

Rapporten må skrives om slik at vi aldri bruker ord som "we" og "our". Isteden kan det byttes om med "the group" eller så kan setningen skrives om

• Erik
• Eskild
• Olga
• Sebastian
• Thea
• Una

Can be used in development to get the relevant policies for each goal/subgoal, to be added to the ontology.

Find a time to meet up and fill in the forms on BB.
Due by the 17th at 12PM(!)

• Thea
• Una
• Eskild
• Olga
• Erik
• Sebastian

• Norwegian
• English
• Spanish
• German
• French
• Portuguese
• Dutch?

• Update component diagram with new components
• Update sequence diagram. Remove login and validation process. Mention in the relevant section instead.
• Update use case diagram to include the language features.
• Update state diagram with languages
• Update communication diagram (?)
• Update deployment diagram
  …

(- [ ] Search across languages)

• Retrieve language filtered documents
• Change prefix from rdf to SDG
• Temporary support for only language code using string manipulation
• Get language code instead of language URL
• Pagination support
• Add support for multi-language, prioritized results

(#11 related)

• Sprint diary for Edgar
• Update release plan
• Requirements
• System architecture
• Test plan
• Project management
• Group organization
• Development process
• Tools to support our work

• Write GET request-bonanza script
• XML to JSON

• Erik
• Eskild
• Olga
• Una

• Make language component
• Make files for localized strings
• Magic

• Municipality view isn't working because of errors in the query, apparently (400 response)
  Example scenario/call sequence/thing:
  Frontend
  GCDViewMunicipality.tsx contains GDCView.tsx, then:
  1. loadGDCOutput (in GDCView.tsx)
  2. getGDCOutput (in gdc.ts)
  ----- api.post(gdc/get) call to server ----
  Backend
  1. getGoalDistance (in gdc.ts)
  2. getGDCDataSeries(in getGDCDataSeries.ts) produces an error (code 400, malformed query)

• Graph isn't working when a SDG is pressed because selectedNode is undefined in Graph.tsx, maybe something wrong with ontologyReducer.tsx in frontend/src/state/reducers.

• The list of subgoals under an SDG (SubGoalsGrid.tsx) is not being divided into two parts as intended, and instead shows each subgoal twice.

• Documents show up as nodes in the graph view, massive load time

• Nodes in the graph view are never given a type, and therefore don't display in their proper colors

• The search bar on the front page has stopped working, you can input text, but you won't get any suggestions that you could click to navigate to a different page

• Make testable Figma prototype
• Decide type of user test
• Final changes before user test 07/04/22

• Bachelor group report

  • Erik
  • Eskild
  • Olga
  • Sebastian
  • Thea
  • Una

• Master group report

  • Erik
  • Eskild
  • Olga
  • Sebastian
  • Thea
  • Una

• Type of document filter
• Active/inactive filter
• Search by keyword