User:Abelard Andedare/WIP/Items
From EVE University Wiki
< User:Abelard Andedare | WIP
Revision as of 22:46, 27 June 2020 by Rayanth (talk | contribs) (Rayanth moved page User:Abelard andedare/WIP/Items to User:Abelard Andedare/WIP/Items: Automatically moved page while merging the account "Abelard andedare" to "Abelard Andedare")
There is a need for expanding the basic information provided by the wiki (in the form of the ship database) to include other items in EVE.
These are my experiments in developing a semi-dynamic Item Database for the wiki, using an external RDBMS hosting:
- a rehosted SDE as a base for the item database
- a set of stored procedures and User Defined Functions for turning the data into something useful for the wiki
- I lean towards Postgresql for the simple reason that it's UDF support is best among open source DBMSs
- a set of templates designed to display item information in a consistent way on the wiki
- an interface between the wiki and the external item database, either using this extension, or something similar
A few things to look out for in the design phase:
- versioning - items tend to get buffed/nerfed/renamed. Depending on wiki-side storage, cron jobs may need to be run to make sure the imported data stays up to date. It is (perhaps) also worth keeping historical changes to items as well (as is done in hoboleaks)
- redirects/maintaining links. If the pages are used in fittings, for instance, how will versioning be done to maintain the intention of the fitting?
- editorializing - will there be a need for information above and beyond that supplied from the SDE? If so, a more sophisticated ETL system will be needed.
- provisioning - what additional demand will this place on wiki server resources? How can it be made as "lightweight" as possible?