#3 and #26 UML added

[yalexublue]

Added 4 files, two pngs and two txt into the designated folder, please confirm the content and decide whether to merge

[waltage]

Please set up a .gitignore file that prevents files like .DS_Store from being committed

[waltage]

#26 Diagram

A few different options for this:

1. Violation >=3 should move right; The user is not going to make the distinction, nor will the frontend, for how many violations have happened; in this case, is the intention that the API automatically deletes the account? Is the account deleted, or is the account suspended (can still view recommendations/share shortlists, just can't post to forum)?
2. Admin initiates the request to delete based on some criteria (>=3 as it's here); in this instance, this should be a separate flow -- the admin will delete accounts for many different reasons beyond just violation >=3; As above, is the account suspended or actually deleted? What is the account suspended from? Can admins change suspension to different services, etc.

[waltage]

Please remove the .DS_Store files, too :)

[yalexublue]

#26 Diagram

A few different options for this:

1. Violation >=3 should move right; The user is not going to make the distinction, nor will the frontend, for how many violations have happened; in this case, is the intention that the API automatically deletes the account? Is the account deleted, or is the account suspended (can still view recommendations/share shortlists, just can't post to forum)?
2. Admin initiates the request to delete based on some criteria (>=3 as it's here); in this instance, this should be a separate flow -- the admin will delete accounts for many different reasons beyond just violation >=3; As above, is the account suspended or actually deleted? What is the account suspended from? Can admins change suspension to different services, etc.

I was thinking give the decision to the super user, so even more than three strikes there might be the case the normal user won't be banned, but I'm find to put it to right side, so to my understanding, if there are more than two violations. The backend will initiate delete. So the Admin is just view post and send out violation counts, would this work? Also I agree it's suspended instead of permanent delete, it would be suspended from gaining any services in front end. Feel free to make change though, I'll do my best give it a go

[waltage]

LGTM

[Pooja-Codes]

Both require changes!

[Pooja-Codes]

Again, missing reply message from backend-->frontend-->admin! How will the admin know if the data has been modified or not?

[Pooja-Codes]

Both diagrams' flow is clear! Great Work!

[Pooja-Codes]

Great Work!!

[Pooja-Codes]

There are commits so we can refer previous-updated things. Discard backups! Otherwise All Perfect!!

[adelaidemz]

Is this just a "status ok" message to the API? Should it go directly under "Store Preferences" (line 13)?

[yalexublue]

It's confirming there's no pending change to user preference also initiate API to start calculating user preference

[adelaidemz]

Are these two lines meant to happen at the end of a user "session", like when they close the site? If so, maybe "compute next matches" instead of first

[yalexublue]

This should happen as soon as we obtain a solid user preference settings. So we will be able to send out data fit user requirement

[jainsvaibhav]

since the discussion is b/w a child and its parent/guardian, I don't think we would need this anymore.

[yalexublue]

Let's keep it for now, I think forum is still to be considered, but should be moved into icebox

[jainsvaibhav]

Please check if we can update otherwise let's keep it as it is.