I am creating a database of procedures that are used by technicians to fix problems. Technicians may need to find a particular procedure by searching for identifying information, or they may need to browse a category of procedures. When a technician needs to fix a problem, he or she will create a ticket for that problem, and employ a procedure to solve that problem. The database should keep track of these tickets and associate them with the employed procedure.As I see it, an entry in the database needs to contain (or reference) the following:
1) The identifying information of the procedure (title, id#, tags, etc..)
2) The content of the procedure
3) A history of associated tickets
I have laid out a solution to this problem, but it was created before it was required that a history of associated tickets be stored along with each procedure. With the addition of this requirement, I am unsure if my method will be effective. This needs to be efficient, and needs to last at least 5 years. Anyway, I'd like some feedback about what you think would be the best way to implement a database like this.My current model uses XML to store all the relevant information in a single file. the filename will serve as the unique ID number of each procedure, and the identifying information, as well as the content, will be stored as meta-data using appropriate < > tags. A stand-alone application will be written that provides the user with the required search features. It would be desirable to embed this application in a mediawiki environment.
1) The identifying information of the procedure (title, id#, tags, etc..)
2) The content of the procedure
3) A history of associated tickets
I have laid out a solution to this problem, but it was created before it was required that a history of associated tickets be stored along with each procedure. With the addition of this requirement, I am unsure if my method will be effective. This needs to be efficient, and needs to last at least 5 years. Anyway, I'd like some feedback about what you think would be the best way to implement a database like this.My current model uses XML to store all the relevant information in a single file. the filename will serve as the unique ID number of each procedure, and the identifying information, as well as the content, will be stored as meta-data using appropriate < > tags. A stand-alone application will be written that provides the user with the required search features. It would be desirable to embed this application in a mediawiki environment.