-
Notifications
You must be signed in to change notification settings - Fork 0
Magazine User Relations
kalyankk edited this page Mar 17, 2020
·
3 revisions
Magazine admin userId details along with permissions will be stored on magazine collection
These details will be stored in a separate collection.
| id | magazineId | magazineCode | userId | userName | magazineUserRole | referenceId | startYear | endYear | fileUrl | requestedOn | updatedOn | updatedByUserId | updatedByUserName | status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 29 | cmrec | 385 | someuser | student | HT018423 | 2018 | 2022 | NULL | 2020-02-23 16:04:02 | 2020-02-24 09:54:12 | 3753 | cmrecadmin | approved |
| 2 | 34 | vbit | 357 | aksh1 | alumni | HT0108276 | 2010 | 2014 | https://s3.bt.stmagz.com/files/389539r.jpg | 2020-03-01 03:13:16 | NULL | NULL | NULL | Pending |
| 3 | 29 | cmrec | 242 | laxma1 | faculty | EMP214 | 2019 | NULL | https://s3.bt.stmagz.com/files/389g34t.jpg | 2020-03-05 13:00:22 | 2020-03-07 11:35:43 | 3753 | cmrecadmin | rejected |
- index should be done on magazineId, userId, startYear and status
Approved user are not allowed to perform any other operation on magazine entities except follow and getting the feed.
While onboarding, user selects a college as a student / alumni / faculty. Else user can also add college from education / experience from bio page.
In both cases, if the college has a magazine with stumagz, join request (Magazine_User) will be created and the same needs to be approved / rejected by magazine admin.