70 likes | 152 Views
PCD Data Management. An ill-disciplined plethora of sources. Ihe.net wiki.ihe.net ftp.ihe.net I think it’s fair to say that the organization of these is a shambles. Some important things exist in successive versions. Ought to be controlled like any persistent development artifacts
E N D
An ill-disciplined plethora of sources • Ihe.net • wiki.ihe.net • ftp.ihe.net I think it’s fair to say that the organization of these is a shambles
Some important things exist in successive versions • Ought to be controlled like any persistent development artifacts • Microsoft Word and its discontents • Other possibilities include W3C xml form, DocBook, DITA, etc.
Makeshifts that we use • Dates embedded in filenames • Nice thing about ISO 2601 dates (2012-10-17) is that if you put them in a consistent place in the filename, then the files can sort chronologically in directory listings
So how about a conventional version-control system? • Subversion – svn • Open source; popular with open source projects • An improved descendent of familiar old systems: RCS, CVS • Supported on pretty much any platform • Plays nicely with other tools • Nice, free Windows UI: TortoiseSVN
GForge • Version control with benefits • Supports svn version control system (among other) • Used by IHE; also used by HL7 so if you deal with both, you only need to learn one version control system
IHE’s Gforge • Supported by France’s INRIA: gforge.inria.fr • Looked after by Eric Poiseau • To use: ask Eric for a Gforge account • Install and study Subversion a little • Link to INRIA’s Gforge • Caution: your firewall may not be friendly to svn protocol – https version more likely to work