Design Discussion - 09 Feb 23

[chrisvrose]

• Discussed design diagram

1. Hierarchy

• Dynamic
• Let's hardcoded for now, we can extend to use templates later

2. Entities

• Transactions and Events can be merged into one - Request Form

3. The current status is a index to the current pending review.
4. If approved, increment.
5. If rejected, mark Final status as reject, ask user to submit a new request

[chrisvrose]

Entities

• Request form

  • Form Id : int
  • Event title
  • Requester: User id
  • Creation/Updation Date
  • Type: String (Financial/Normal)
  • Request Hierarchy : List<Role>
  • Current Status : int
  • Final Status: PENDING | ACCEPT | REJECT | CANCELLED
  • review log : List<Review Log>
  • Form PDF: Blob

• Review Log:

  • Form Id: int
  • who: User
  • what: ACCEPT | REJECT
  • what they've said: Optional<String>

• User

  • User id
  • Name
  • Email id
  • Role: Role
  • Phno#
  • Password (Hashed)
  • Society : Optional<Society>
    • null if execom
  • Execom: boolean
  • Created/Updated
  • enabled

Role -> Society Execom | Main Execom | Faculty Advisor | Finance Head | Branch Counselor | Admin

• Society
  • Name: String
  • Email: Optional
  • isActive: boolean
  • createdAt/updatedAt

[chrisvrose]

LocalDateTime for dates

[Prajwalprakash3722]

can set default TZ on Db anyway

[Prajwalprakash3722]

Do we need to normalise the tables?, to 3NF at least

[chrisvrose]

I think the way we did it, it does fit 3NF

[Prajwalprakash3722]

I believe so, no harm in verifying again

[Prajwalprakash3722]

Draft DB Diagram