Aish_Create buildingTools.js

[Aishwaryak01]

Created model file for buildingTools.js which consists of schema to hold various attribute information related to tools.

Description

Created model file for buildingTools.js which consists of schema to hold various attribute information related to tools.
WBS # 4.4.1 from Phase 2 WBS document

Related PRS (if any):

NA
This is a backend PR

Main changes explained:

• Created a model file buildingTools.js which consists of a schema to hold various attribute information related to tools.
• The tool's information is stored on an individual basis.

How to test:

1. check into the current branch
2. do npm install and ... to run this PR locally
3. Navigate to HGNRest\src\models\bmdashboard\buildingTools.js
4. Check if all tool-related attributes are listed in the schema.

Note:

This is just a draft of the schema. Once the schema is finalized a collection will be made in the MongoDB database.

[tdkent]

• schema name should be buildingTool since its a singular item and not plural?
• field inventoryItemId can be changed to itemType: { type: mongoose.SchemaTypes.ObjectId, ref: 'buildingInventoryType' }
• the image field should probably not be required for now, as it will be quite difficult to test
• can you explain what the total and availableCount fields are for? I'm not sure they're needed if the model is used to track a single item, but I might be missing something.
• Will the default value of the condition field cause an error since it's not in the enum? Should the default instead be 'Good'? See also purchaseStatus, should that even have a default value?

[Aishwaryak01]

• schema name should be buildingTool since its a singular item and not plural?
• field inventoryItemId can be changed to itemType: { type: mongoose.SchemaTypes.ObjectId, ref: 'buildingInventoryType' }
• the image field should probably not be required for now, as it will be quite difficult to test
• can you explain what the total and availableCount fields are for? I'm not sure they're needed if the model is used to track a single item, but I might be missing something.
• Will the default value of the condition field cause an error since it's not in the enum? Should the default instead be 'Good'? See also purchaseStatus, should that even have a default value?

@tdkent :

schema name should be buildingTool since its a singular item and not plural? - Sure.Made the change

field inventoryItemId can be changed to itemType: { type: mongoose.SchemaTypes.ObjectId, ref: 'buildingInventoryType' } - Done

The image field should probably not be required for now, as it will be quite difficult to test - Removed it.

Can you explain what the total and availableCount fields are for? I'm not sure they're needed if the model is used to track a single item, but I might be missing something. - I thought this schema was for plural tools so thought of adding the total count and how many of them are available to rent. I now get it that this should be taken care of in inventory.

Will the default value of the condition field cause an error since it's not in the enum? Should the default instead be 'Good'? See also purchaseStatus, should that even have a default value? - Sure.Made changes.