citizensciencecenter / backend Goto Github PK

☐ Create
☐ List
☐ Search
☐ Retrieve one
☐ Delete
☐ Update

If a username is not set (as just an email is required by default), then this should be set by the backend to save handling this in the various frontend clients

☐ Create
☐ List
☐ Search
☐ Retrieve one
☐ Delete
☐ Update

Currently, a project space is made for every new user created.
This should be modified so that users must register in order to create activities but can still take part in others

https://docs.min.io/docs/upload-files-from-browser-using-pre-signed-urls.html

Use a decorator to confirm if the user is able to create a submission AND if they have submitted before

Specify roles in openapi spec and use access checks to ensure the user has those rights

Do not delete user but set all info to DELETED and set to inactive.

Question: Should their personal info (location or age etc) be kept or anonymised or deleted?

☐ Create
☐ List
☐ Search
☐ Retrieve one
☐ Delete
☐ Update

Allow anonymous users prefix to be specified in the config file and used, instead of defaulting to anon

File: BasicProfileEditor.vue
Username check
checkUsername() {
let query = {
'select': {
'fields': [
'*'
],
'tables': [
'users'
]
},
'where': [
{
"field": 'username',
'op': 'e',
'val': this.form.username
}
]
};
this.$store.dispatch('c3s/submission/getSubmissions', [query, 1] ).then(res => {
console.log('username checked');
console.log( res );
if( res.body.length > 0 ) {
// email already registered
this.errors.username = true;
}
});
},
Error:

Profile Save

save() {
  console.log( 'save user ');
  this.$store.dispatch('c3s/user/updateUser', [ this.currentUser.id, this.getUserObject() ] ).then(r => {

    console.log( r );
    this.$store.dispatch('c3s/user/validate').then(v => {

      console.log( v );

    });

  });
}

Error:

Projects and activities do have a lot in common, linguistically.
Possibly renaming projects to team or group but allow activities to be created outside of a group as well?

☐ Create
☐ List
☐ Search
☐ Retrieve one
☐ Delete
☐ Update

In clients, referencing models by ID can result in extra calls and make them harder to read.
Proposal to use names as the ID, or composite with owners.

Tasks and projects can be deleted but this needs to provide the warning that all submissions and media relating to them will also be deleted immediately

Potentially add a deleted state and prevent login
This requires Terms and Conditions to say that identifiable information would be kept as it may link to past projects
Maybe delete identifying info (email etc)