We have both a simple and a complex structure! Simple in the sense that the vast majority of courses in BB are one year taught MSc programmes, complex in that several schools (1 School = 1 Faculty for us now) use a modular course structure and those modules can be shared in different combinations between courses and options, some students may have 15 bb coursesites during the year. Our preferred naming syntax is
Programmes are designated by
SCH-YY-MSC-CID
Where:
SCH is a faculty identifier (would like 3 characters but one has 2)
YY is two character id for the academic year (starting so 07 or 08 etc)
MSC is the intended qualification (sometimes there is more than one award but the owner is usually MSC)
CID is the course ID used (ideally) in our student records system - sometimes we have to munge it to get 3 characters
An example would be SAS-08-MSC-LAM which is MSC in Land Management in the SAS faculty that starts October 08
Modules are designated by
SCH-YY-MID
Where SCH and YY are as above
MID is a unique module code, we have 2 parts a number which is the module and a prefix letter which is the significant version.
An example would be SAS-08-A1080 which I happen to know is the 08 edition of General Management module (original version) "owned" by the SAS faculty. In this particular case it is a module that appears in about 8 programmes.
For generically owned material (campus or department - HR / IT etc) we change the SCH / MSC code to denote the owner and tend to use sequential numbering.
What it did highlight when introduced was that we needed to be consistent in the syntax used to create course and module codes in the SR system as it had knock on affects not only to the VLE but elsewhere that had not been appreciated.
Peter
--
Peter Harrison
Learning Technologies Manager - IT Department
Cranfield University - Cranfield - Bedford - MK43 0AL
T: 01234 754097
E: [log in to unmask]
-----Original Message-----
From: Blackboard/Courseinfo userslist [mailto:[log in to unmask]] On Behalf Of Andy Turner
Sent: 12 November 2008 11:49
To: [log in to unmask]
Subject: Re: [BLACKBOARD-USERGROUP] What conventions do you use for naming Blackboard coursesites?
We take data from our MIS to create
* course templates e.g. 5CFCTGA00E_TEMPLATE
* dated course instances e.g. 5CFCTGA00E_17-SEP-07_07-JUN-10
Basic course codes stay the same from year to year, hence our need to
add the start and end dates.
The MIS uses different coding conventions for Programmes and Modules,
and for FE and HE courses. If you know what type of course you're
looking at, you can glean some information from the code e.g. Faculty,
HE level, site.
I must admit that the length and complexity of the codes does make it
difficult for most staff to commit them to memory, but at least we know
that what we have in Blackboard tallies with the MIS.
Andy Turner
Manager, Online Systems Group
Thames Valley University
Tel. 0118 967 5521
[log in to unmask]
> -----Original Message-----
> From: Blackboard/Courseinfo userslist [mailto:BLACKBOARD-
> [log in to unmask]] On Behalf Of CLAY Gary M
> Sent: 12 November 2008 11:10
> To: [log in to unmask]
> Subject: What conventions do you use for naming Blackboard
coursesites?
>
> Hello, I'm interested in learning what naming conventons are used for
> coursesite (specifically the course id) at other institutions.
>
> We currently combine module code and start / end dates but this can
> become complex to interpret so I'm looking at other options.
>
> If there's demand I could present the findings e.g. at Durham perhaps?
>
> --------------------------------------------------
> Gary Clay
> Learning Development Manager
> Academic Development Institute
> Staffordshire University
> Beaconside Campus
> Stafford ST18 0AD
> Telephone +44 (0) 1785 353648
> e-mail [log in to unmask]
>
>
> The information in this email is confidential and is intended solely
for the
> addressee. Access to this email by anyone else is unauthorised.
>
>
>
> If you are not the intended recipient, any disclosure, copying,
distribution or any
> action taken or omitted to be taken in reliance on it, except for the
purpose of
> delivery to the addressee, is prohibited and may be unlawful. Kindly
notify the
> sender and delete the message and any attachment from your computer.
|