Fraser to Mayor and Council, February 22, 1933; Ottawa Journal, August 22, 1932; BCEP, Diary of I.
Diamond Taxicab Association Limited, A Review of Operations, December 30, 1942;" Hamilton Spectator, May 4, 1934; Ottawa Journal, February 3, 1932; BCEP, Ivor Neil, Brief on Existing Conditions of the Taxicab Industry and the Proposed Bylaw, July 27, 1933.
BTTC, January 1930, 37; May 1930, 21; January 1931, 20; BCEP, Memo from I.
BCEP, Report of the Independent Taxicab Owners' Association on the Taxicab Industry in the City of Vancouver, September 1933; Diary of I.
BCEP clarifies that the city council, the city solicitor and police officials, the electric railway, and taxi owners' association asked the provincial legislature for the power to limit licenses, as was being done in Toronto (whose 1932 taxicab report provided the paradigm for Vancouver regulation).
The BCEPS was preloaded with the names of studies and research sites.
The BCEPS was designed to allow access by multiple CRSs and research organisations in different provinces.
We implemented the BCEPS at one site at a time to ensure that the system functioned optimally.
Challenges were encountered with the installation at some non-MRC sites: the BCEPS could not run on a 64-bit platform until an upgrade was performed; some organisations had to open hypertext transfer protocol secure (https) ports on their gateways before the BCEPS could be implemented and operate optimally.
Prior to BCEPS implementation, we preloaded all studies being conducted at a CRS on to the system (Fig.
Participants who were found to be co-enrolled during the CAPRISA 004 and HPTN 035 clinical trials were 'flagged' as co-enrollers on the database by the MRC IT department at BCEPS implementation.
The BCEPS is monitored and quality-controlled on a daily basis by comparing the CRS participant registration log with a BCEPS attendance report.