Extension:Cargo/Known bugs and planned features

Cargo - navigation
Basics	Main pageExtension:Cargo (talk) · Download and installationExtension:Cargo/Download and installation · Quick start guideExtension:Cargo/Quick start guide · Other documentationExtension:Cargo/Other documentation · SMW migration guideExtension:Cargo/SMW migration guide
Using Cargo	Storing dataExtension:Cargo/Storing data · Querying dataExtension:Cargo/Querying data (Display formatsExtension:Cargo/Display formats) · Browsing dataExtension:Cargo/Browsing data · Exporting dataExtension:Cargo/Exporting data · Other featuresExtension:Cargo/Other features
Resources for help	Common problemsExtension:Cargo/Common problems · Known bugs and planned featuresExtension:Cargo/Known bugs and planned features · Getting supportExtension:Cargo/Getting support
About Cargo	Authors and creditsExtension:Cargo/Authors and credits · Version historyExtension:Cargo/Version history · Sites that use CargoExtension:Cargo/Sites that use Cargo · Cargo and Semantic MediaWikiExtension:Cargo/Cargo and Semantic MediaWiki · FAQExtension:Cargo/FAQ

Known bugs

• The buttons in the 'calendar' display format (like "today") currently still have their values hard-coded in English.
• There is currently no way to query on fields that hold a list of coordinates.
• If a table is recreated via the web interface and the "job run rate" (set via $wgJobRunRate) is too high, it can lead to some pages not getting their data stored.
• Cargo has in the past experienced issues in both storing and displaying data when the VisualEditor extension is also in use on the wiki; it is not clear if this still a problem.
• Cargo is known to work with the MySQL, PostgreSQL and MS SQL Server database systems. It has not been tested with either Oracle or SQLite, and most likely will not work with either one.

Planned features

Features that it would be useful to add to Cargo include:

• More display formats, including slideshows and more complex charts.
• Allow for defining "child tables" for templates, so that all templates that show up together on certain pages can be queried and displayed together more easily, especially in Special:Drilldown.
• Better automatic display of data, including automatic maps, calendars/timelines and bar charts for tables that contain fields of type Coordinates, Date/Datetime and Integer/Float, respectively.
• Allowing for defining a field's allowed values to be a hierarchy, rather than just a simple list - for use in forms, drilldown and possibly queries (i.e., querying on a field matching some value and getting back the set of pages where the field matches not just that value but its children values).
• A new "Ratings" field type, which would have special handling in forms and drilldown.