Users do not want to have to register to use the application therefore the solution is to create a user slug (random string generated from core-service /Users api). One requirement is that the user slug should not be in the url at any point. However the user slug is required for a user to be able to POST a classifier to the core-service and to be able to save classifiers (queries from the query builder) before sending them to ML tasks.
It would be preferable to have some sort of "getUserLink" functionality so that an authenticated user would have reference to return to their account.
bdolly
commented
7 years ago
Users do not want to have to register to use the application therefore the solution is to create a
user slug(random string generated from core-service /Users api). One requirement is that theuser slugshould not be in the url at any point. However theuser slugis required for a user to be able to POST a classifier to the core-service and to be able to save classifiers (queries from the query builder) before sending them to ML tasks.It would be preferable to have some sort of "getUserLink" functionality so that an authenticated user would have reference to return to their account.
Layout and Documentation for the User Profile view can be found in the UI/UX wireframes.