The important things to log are (in no particular order):
When: Time frame
Who: The person or persons involved
Where: the locations involved
What: The objects involved
How: The process that was performed (e.g. replace, fix, switch off and then on)
What the database would require are:
Time
People
Places
Objects
Processes
One other aspect of this database that would be useful is booking equipment. But this could be thought of as a process?
Time:
Start time
Predicted end time
End Time
People
Login Name
Contact Details
Places:
Geographical
Room Number
Objects:
Serial Number
Make
Model
Specifications
Processes:
Type of process
An few working examples to help design the database:
A new iMac has just been delivered to the college and is put in a computer suite:
- The database is logged onto with Username and Password
- A process is selected called: Add item to inventory
- User adds:
- Make
- Model
- Serial Number
- Organisation made Serial Number
- Specifications
- Room
A student would like to borrow an iPad:
- The database is logged onto with Username and Password
- A process is selected called: book out item
- User selects
- type of item:
- Make: Apple
- Model: iPad 2
- Time from: Today at 12:15
- Time until: Today at 16:00
- User is show whether any iPad 2's available for that time
- User confirms booking
- User sees instructions
Well, just having another look at the database and found this nice little helpful question and answer about querying a database to find 'free' items. Also describes the database very nicely using MySQL (need to learn this)
I'm thinking about making it in Access and then exporting it to MySQL? Or perhaps I should just delve straight in?
Ready made alternatives:
Here is a list of starting points for different systems:
Drupal - Merci module - this looks good!!
Drupal - Resource booking
Drupal - Resource conflict
No comments:
Post a Comment