| Version 79 (modified by , 11 years ago) ( diff ) |
|---|
Welcome to the LCBRU Informatics Platform wiki
- Public links
- BRICCS public web page
- LCBRU studies supported
- BRICCS - where it all began
- DHF - Diastolic Heart Failure
- DREAM
- GENVASC - recruitment across primary care
- HDL ethnicity - a study into HDL across ethnic groups
- MVO - Microvascular Obstruction
- NIHR Bioresource - contributing to a national facility for translational medicine
- PRESTIGE
- SCAD - Spontaneous Coronary Artery Dissection
- TOTAL - Routine aspiration thrombectomy versus PPCI alone
- Planning
- Component pages
- C3PR
- caAERS
- CaTissue
- API Client - 'Sampler'
- BarCodeReaders - notes on the various input devices reading linear and 2d barcodes
- CaTissueUpgrade - notes on the upgrade process to v1.2
- Building & Deploying caTissue application from the source code in Ubuntu
- CiviCRM
- ClinicalRegistry
- Drupal
- EDGE - possibly
- i2b2
- i2b2 - Plugins
- i2b2 - Customisations
- i2b2 - caTissue integration
- i2b2 - UHL clinical informatics system integration
- i2b2 - primary care informatics systems integration
- i2b2 - Onyx import
- i2b2 - fixes
- i2b2 AUG
- Query Tool and Analysis Types
- Ontology and CRC:
- i2b2 - Documents
- i2b2 - DB Basics
- i2b2OntologyCRC-1 Discussion, questions, things discovered
- Snomed CT Discussions regarding mapping legacy data to Snomed CT for data management
- c_metadataxml Column holding metadata associated with lab findings
- i2b2 - Web Services
- IdLabelPrinting
- MRBS
- Onyx
- OnyxCode
- OnyxQuestionnaire - Developing (and Maintaining) a Questionnaire
- OnyxDeployment - Deploying a Questionnaire
- OnyxPrismClient
- Onyx Export and Purge
- OnyxExportOntology Discussion on deriving an initial ontology
- OnyxTestSystem
- OnyxVersions
- OnyxDatabaseReporting
- OnyxDataValidation
- Onyx to PDO Assumptions underlying importing facts into i2b2 from the BRICCS questionnaire
- PMI Lookup
- RealWorldRecruitment
- REDCap
- Infrastructure components
- SystemAdmin system admin for the BRICCS infrastructure.
- ServiceDeployment recommendations for flexible service deployment
- Subversion source code repository
- Trac issue tracking system
- Maven development tool kit
- Eclipse development tool kit
- Backups data backup requirements
- SSH ssh keys and configuration
- DNS DNS configuration for
briccs.org.uk - JBoss Settings, experiences and gotchas from working with the JBoss Application Server
- VirtualBox VirtualBox commands and bugs
- Oracle Oracle commands, gotchas and bugs
- MS SQL issues MS SQL Server commands, gotchas and bugs
- Miscellaneous
- User pages
Trac notes
Trac is a minimalistic approach to web-based management of software projects. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress.
All aspects of Trac have been designed with the single goal to help developers write great software while staying out of the way and imposing as little as possible on a team's established process and culture.
As all Wiki pages, this page is editable, this means that you can modify the contents of this page simply by using your web-browser. Simply click on the "Edit this page" link at the bottom of the page. WikiFormatting will give you a detailed description of available Wiki formatting commands.
"trac-admin yourenvdir initenv" created a new Trac environment, containing a default set of wiki pages and some sample data. This newly created environment also contains documentation to help you get started with your project.
You can use trac-admin to configure Trac to better fit your project, especially in regard to components, versions and milestones.
TracGuide is a good place to start.
Enjoy!
The Trac Team
Starting Points
- TracGuide -- Built-in Documentation
- The Trac project -- Trac Open Source Project
- Trac FAQ -- Frequently Asked Questions
- TracSupport -- Trac Support
For a complete list of local wiki pages, see TitleIndex.
