Hello all, Below is the common database contributors FAQ. I hope it explains what we are trying to achive. We still need more volunteers, there are a couple of major omissions at the moment; the US services and the Russian Navy. Robert ---------------------------------------------------------------------------- Robert Stone (rds8@ukc.ac.uk), 1996 Harpoon II Common Database Contributors FAQ ------------------------------------------- Common database keeper: Saul H Jacobs (sjacobs@flash.net). FAQ maintainer & recorder of who's doing what: Robert Stone (rds8@ukc.ac.uk). Country.dat file maintainer: Facundo Bonaldi (bonaldi@overnet.com.ar). 1. Statement of Aims -------------------- The common database project is the creation of a Harpoon II platform database that is correct and includes platforms useful for scenario writers. This takes the form of correcting errors in the existing platform entries and the inclusion of new platforms. The result should be a database that improves the Harpoon II 'game', not mearly a reference work. 2. What contributors need ------------------------- The minimum is a copy of Harpoon II, access to some reference works (Harpoon miniatures, big name reference books like Janes or other smaller name reference books) and time. The preferred is the above and a copy of Tom Wenck's platform editor and the Harpoon II scenario editor, so you can test your changes. 3. What to do ------------- The common database project can be broken into two parts: Correcting errors in the existing database and adding new platforms. These should then be sent to Saul (the common database keeper). 3.1. Correction of errors The modification of the existing platforms in the database should both correct errors and bring platforms up to their current standard (incorporate in-service improvements and modernisation). This may require the creation of new equipment (see 4.2 below). 3.2. New platforms The creation of new platforms should be restricted to platforms that are directly relevant to Harpoon II, for example frigates but not harbour launches. It is not practical to try to include every single class of vessel or type of aircraft in the database. This means contributors need restrict themselves to the types of platform that are likely to be needed in numerous (certainly more than one) scenarios. Hypothetical platforms should be restricted to those that are integral to scenarios or to those that are due to enter service in the near future, e.g. F/A-18E, JAST/JSF, Tornado GR.4. (See section 6 below) 3.3. Submissions Once you have a number of error corrections recorded (see 4.1 below) and/or have a number of new platforms (see 4.2 below) you should email them to Saul (at sjacobs@flash.net). The number of corrections you record or new platforms you create between submissions to Saul is your choice, but I would suggest submitting to Saul when you have corrected two or more platforms (ships, subs or aircraft) or when you have created one or two new platforms. In other words I would suggest keeping a steady stream of submissions to Saul, so the common database continually evolves. 4. How to do it --------------- This sections gives some details on creating correction lists and creating new platforms. I would like to point out that working with a multi-tasking operating system (OS/2, Win95, etc.) makes life much easier. I have the platform editor running side-by-side with the editor I am using to record my corrections. Often reference sources disagree. Janes says one thing, Combat fleets another. In this situation you need to apply common sense, if two sources say one thing and only one source says something different, then the two sources that agree are probably right (unless you have reason to believe otherwise, like the two agreeing sources are old and may be out of date). So you will need to make a pragmatic decision to which source you believe is correct. 4.1. Standard correction lists It would make it easier if all correction lists were in the same format. I would like to suggest that using the platform editors menu titles with the corrections listed under these titles. This is best demonstrated by an example: Type 21 F 169 Amazon (ID37) 1. Name, etc. 2. Damage Points, etc. DP 84. 3. Air Facilities 4. Engines or Fuel 5. Sensors Add Type 182 (ID1154) {360} and UAA-1 (new TPF) {360}. 6. Mounts Add 2x 20mm (ID56) {1:PMA & PMF, 1:SMF & SMA}. 7. Magazines Remove Sea Cat Mod 1, Mk46 LWT and Sea Skua magazines. Add Type 21 (new TPF), Mk8 (ID118) and 20mm (ID68) magazines. 8. Communications Add SATCOM (ID43). 9. Codes Add Aluminum Superstructure. The platform editor ID numbers needed for the corrections are included (where possible) prefixed with the letters ID and placed in brackets. New equipment that is included in the submission in a TPF file are identified by (new TPF). Mount and sensor arcs are recorded in curly brackets {}, with either the platform editor names of arcs (e.g. PS, PMA, SMF) and/or the number 360 to indicate 360 degree coverage. So {1:PMA, 1:SMA} denotes that one thing should have the arc port-mid-aft and the other starboard- mid-aft, {PMA & PMF) denotes the arc port-mid-aft and port-mid-forward. I've also combined the 360 and platform editor notations for convenience, e.g. {360 - PS & SS} denoted 360 degree minus port and starboard stern arcs. 4.2. TPF issues The contents of TPFs submitted to Saul should be documented using the format used for correction lists (see 4.1 above). This is so any problems from including your TPF into the common database can be found and fixed. When creating new equipment you need to be aware that adding TPFs to the database may cause duplication. Saul is trying to avoid duplication in the common database, so checking for duplication by adding your TPF to a copy of the common database and then checking for duplication (I do this by creating indexes in the platform editor and then checking the new entries at the end of the indexes) would be helpful. Therefore you may find that a new piece of equipment results in a lots of duplication, the best thing to do then is to document the equipment and just submit the documentation. 5. Who's doing what ------------------- Nation | Navy | Air | | Ships | Subs | Air | Force | -------------------------------------------------------------------------- UK | Robert Stone | Gerald Khoo | Robert Stone | Gerald Khoo | | |+Robert Stone? | | | | | | | | Argentina| <-------------------- Facundo Bonaldi ----------------------> | | | | | | Chile | <-------------------- Facundo Bonaldi ----------------------> | | | | | | Uruguay | <-------------------- Facundo Bonaldi ----------------------> | | | | | | Russia | | | | Michael | | | | | Arkhipov | | | | | | Germany | <--------------------- Tim Lanzendoerfer -------------------> | | | | | | Japan | <------------------------ Kei Hirao ------------------------> | | | | | | South | <---------------------- Stephan Kotze ----------------------> | Africa | | | | | | | | | | Canada | <---------------------- Larry Stephens ---------------------> | | | | | | Other volunteers: Dale Hiller (crossover from WWIII database). Rodney G Graves (once move to Korea is complete). Carsten Mueller (German ships, with Tim, once exams are over). Christian Simon (French Navy, once exams are over). 5.1. Email addresses Saul H Jacobs: sjacobs@flash.net Robert Stone: rds8@ukc.ac.uk Gerald Khoo: G.N.Khoo@lse.ac.uk Facundo Bonaldi: bonaldi@overnet.com.ar Michael Arkhipov: mikea@online.ru Tim Lanzendoerfer: lanzi@t-online.de Kei Hirao: hiraok@ibm.net Stephan Kotze: stephank@iafrica.com Larry Stephens: ab334@issc.debbs.ndhq.dnd.ca Dale Hiller: hillier@morgan.ucs.mun.ca Rodney G Graves: 70651.462@compuserve.com Carsten Mueller: carsten-anton.mueller@uni-duesseldorf.de Christian Simon: 100072.2041@compuserve.com 6. New platforms group ---------------------- At the moment Saul must solely decide on what new platforms are included in the common database. He has suggested that we should set up a group to jointly decide what new platforms are included, this seems the best way forward. I have included in this FAQ some suggested guidelines (see 3.2), these guidelines should be reviewed by the group and modified as required. We therefore need volunteers for this group, whos role will be to review new platform submissions and decide if they should be included in the common database. I would like to suggest that any submitted new platform (TPF) that is not included in the common database should nevertheless be made available from Saul's Platforms Page (http://www.flash.net/~sjacobs/platform.html). 6.1 New platform review group members Saul H Jacobs Robert Stone 7. Country.dat file ------------------- Facundo Bonaldi has volunteered to maintain the country.dat file. So please send all corrections and additions to Facundo (at bonaldi@overnet.com.ar). 8. Additions and corrections ---------------------------- If you have any suggestions for additions or corrections to this FAQ, please email me (rds8@ukc.ac.uk).