Upon navigating to this page, we should fetch the hmis_profile.ttl document from the PASS folder of the user's pod, or create it if it doesn't exist. By default, the profile should contain one top-level RDF relationship describing the user as a http://www.w3.org/2002/07/owl#NamedIndividual. I.E. the ttl file should have at least the following line: <user's web ID> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#NamedIndividual> .
This profile should be fetched and stored through React query, and should be a solid dataset provided by the inrupt javascript react libraries
When the user clicks the next or previous buttons, we should save the profile
If the profile fails to save for any reason, we should display a toast message to the user.
Additional Info
You can see what the general structure of a profile should look like here.
Feature Description
Hook up the page created in this Issue to the solid pod: https://github.com/codeforpdx/PASS/issues/438
hmis_profile.ttldocument from thePASSfolder of the user's pod, or create it if it doesn't exist. By default, the profile should contain one top-level RDF relationship describing the user as ahttp://www.w3.org/2002/07/owl#NamedIndividual. I.E. the ttl file should have at least the following line:<user's web ID> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#NamedIndividual> .nextorpreviousbuttons, we should save the profileAdditional Info
You can see what the general structure of a profile should look like here.