codetanzania / emis-resource Goto Github PK

Possible Properties

name: String
description: String

Task

• Implement domain model on top of predefined data
• Implement http api endpoint
• Update item to use predefined uom than string

I feel like these two things a bit confusing to user. Can't we drop one and remain with only one which will be used to to represent both because they're free text?

Tasks

• Refactor stock domain model
• Refactor stock http api endpoint

Party should not be required on adjusting stock because stock already contain party(owner)

Tasks

• Refactor stock adjustment domain model
• Refactor stock adjustment http api endpoint
• Implement stock transfer between two warehouse
• Implement stock adjustment status i.e request and effective
• Implement stock disposal
• Implement stock purchase

Possible Properties

name: String
description: String

Task

• Implement domain model on top of predefined data
• Implement http api endpoint
• Update item to use predefined categories than string

It seems like stock quantity is not affected when making adjustment.

I thought stock quantity should be dynamically calculated based on adjustments made against particular stock? Is this how it works currently? because I can see stock has quantity property and I don understand if it's static or dynamic property?

Tasks

• Refactor to use item unit of measure
• Refactor to use item categories
• Refactor item domain model
• Refactor item http api endpoint

I suggest this property to be optional. I don't think if the system user do have this information per every stock?

Possible properties

name: String,
geometry: Point,
location: Feature,
keeper: Party,
owner: Party,
capacity: String e.g 23 cbm

Tasks

• should define warehouse name
• should define warehouse location
• should define warehouse owner
• should define warehouse dimensions
• should define warehouse type
• should define warehouse keeper
• should allow geo-searching(near, within etc) for warehouses