Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

OxCAP – Guidelines on training information for training providers

This guidance is consistent with the JISC programme data definitions (version 3). Training providers may find it useful to look at the JISC document: http://www.xcri.co.uk/KbLibrary/XCRI_CAP_Data_Definitions3.0.docx

There are related vocabulary files: http://www.xcri.co.uk/what-is-vocabularies.html these include:

http://www.xcri.co.uk/vocabularies/studyMode2_1.xml http://www.xcri.co.uk/vocabularies/attendanceMode2_1.xml http://www.xcri.co.uk/vocabularies/attendancePattern2_1.xml http://www.xcri.co.uk/vocabularies/languages.xml

The core elements in XCRI-CAP 1.2 are catalog, provider, course, presentation, qualification and credit. Location is slightly different, because it can occur within the context of a provider as an entity offering courses, or within the context of a provider as an entity relating to the venue of presentations. At oxford we are not too concerned with qualification or credit. The relationship between the core elements is shown above.

General guidelinesIt is recommended that unless otherwise stated, all textual fields are restricted to 4000 characters (including mark-up). Training information for OxCAP should be consistent with other published sources of information (websites, graduate prospectuses etc) unless there is clear reason for the information to be different

Training must be real, existing training and training information must be verifiable. In other words, do not include pie-in-the-sky courses that may possibly get run one day.

If you have other bits of data that you want people to see then please include let us know.

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

Do not include courses that you do not want to be either in the WebLearn SES interface or in the public feed.

Course data supplied as a CSV or Excel XML FileCSV or .xslx XML files should be uploaded to the ‘uploaded CSV and xslx files’ folder on the ‘Shared Documents’ page in the Share Point site: https://sharepoint.nexus.ox.ac.uk/sites/OUCS/coursedata/ aka http://tinyurl.com/oxcap-entry please let us know if any of the columns given below should only be shown behind a password in WebLearn (and not on public websites).

CSV files should be delimited with reference to RFC-4180: http://tools.ietf.org/html/rfc4180. The salient points here are that:

1. Strings should be enclosed in quotes2. If a string contains a quote then this should be double escaped3. Newlines may appear in the file so long as they are in between quotes (or else the newline

will be assumed to initiate a new record)4. Use a comma to separate ‘columns’5. Do not include column headings

Take as an example

“Words, and, commas”,“A quote “” in a string”,“newline”,128,”Final string”

This should be read in as:

Words, and, commas A quote “ in a string newline

128 Final string

Course data supplied via Share Point Courses may be supplied by entering data into a form hosted in the ‘Course Data’ Share Point site: https://sharepoint.nexus.ox.ac.uk/sites/OUCS/coursedata/ (which also has the short URL http://tinyurl.com/oxcap-entry)

Course data supplied by XML feedOXCAP has the following namespace:

http://purl.ox.ac.uk/oxcap/ns/

there are a handful of attributes and two tags <oxcap:memberApplyTo> and <oxcap:session> defined within the above namespace.

Course data fields

The number in parentheses is the column number in the CSV file. The XCRI-CAP element is shown in parentheses after the name of the field.

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

Provider

Mandatory(1) (A) Identifier (XML: catalog >> provider >> identifier) – use the 4 character department code

(“PRAS code”) or 2 letter sub-department code (“twoThree code”) of unit providing the training, eg, 3C01 for Area Studies , 6FA0 for the Language Centre or GB for Careers. Alternatively, if the training provider does not have a PRAS code then one may use the appropriate OxPointsID. NB this must have been agreed with IT Services first.

Training Provider OxPoints IDITLP 53505808Philosophy Faculty Library 10000000Theology Faculty Library 10000001

(2) (B) Title (XML: catalog >> provider >> title) – Official title of training provider.

Optional(3) (C) Description (XML: catalog >> provider >> description) – max of 4000 characters. JISC say:

General textual information about the provider and its facilities. May include more complex details about how enquiries are made than the <location> element, for example how to obtain prospectuses, contact details for international students and so on.

(4) (D) URL (XML: catalog >> provider >> url) – The website of unit providing the training. This should be appropriately encoded so it conforms to IETF RFC 3986, ie, no spaces

Course / Presentation

Mandatory(5) (E) Title (XML: catalog >> provider >> course >> title & catalog >> provider >> course >>

presentation >> title1) – of the item of training/course, max 255 chars - should be around 50 characters and eight words in length and should refer only to the content of the course. Must be unique and comparable across all of Oxford and useful to students, eg, do not call your course "Research Methods" chose a title to distinguish it from other research methods courses, eg, "Research Methods for Politics Students".

(6) (F) Identifier (XML: catalog >> provider >> course >> identifier) –each item of training needs a unique identifier. DAISY uses the following scheme; we would be happy if this scheme were adopted.

The module code should have a fixed length of 10 digits and use the University (PRAS) organisation chart codes for departments and sub-units (see http://www.admin.ox.ac.uk/pras/uniorg/ )

The module code consists of three parts:

1. the 4 digit department code (e.g. ‘3C01’ for Area Studies) directly followed by1 Oddly the title of the presentation cannot be inherited from the parent Course

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

2. the 2 digit sub-unit code (e.g. 'MH’ for African Studies, '00' is there is no sub-department) and again directly followed by

3. a 4 digit serial number using leading zeros as needed (e.g. ‘0001’).

In this example, the complete module code will be ’3C01MH0001’.

The first elements of the code will remain constant within a department (and the second and third within a department or a sub-unit); the fourth, serial number part, should increment for each successive training module entered.

If the training provider has been identified by OxPointsID instead of a PRAS code then append a dash to it and use this to prefix the serial number, e.g., 10000001-0004

(7) (G) Visibility (XML: catalog >> provider >> course | oxcap:visibility attribute) – of the item of training/course. Either “PB” ( = Public) - default or “RS” ( = Restricted) or “PR” (= Private). It is assumed to be public unless you say "restricted" in which case the course will be seen only within the SES tool in WebLearn and will not appear in the public feed. This is mandatory only if it does not hold the default value. A course can also be marked as "private", meaning it will not appear anywhere, but preferably such a course would not be included in the feed at all. This should be a drop down list on Share Point data entry site.

(8) (H) Oxford Users Booking (XML: catalog >> provider >> course >> presentation >> oxcap:memberApplyTo & used in catalog >> provider >> course >> presentation >> applicationProcedure) - a URL where one can book, ie, a URL to either the booking system or (preferably) the page in the booking system where one can book for this specific instance of the course. See below for further explanation.

(9) (I) Public Booking (XML: catalog >> provider >> course >> presentation >> applyTo) – For CSV files and Share Point data entry this is a URL (or ‘mailto:’ email address) where external users can request a place. It may make sense to use the URL of your training website (or main website) if the public are not allowed on your courses just so they can read about the courses. I suggest that if there is no applyTo, user-facing systems can use the URL (Column 22 (V)) if it has been supplied, otherwise there will be no link.

In XCRI-CAP is intended that the values for ‘(Member) Apply To’ and ‘(Public) Apply To’ can be strung together to form XHTML that can be used in the ‘applicationProcedure’ element. This is necessary as only (zero or) one occurrence of ‘applyTo’ element is allowed. An example of this would be:

<applicationProcedure><div xmlns="http://www.w3.org/1999/xhtml"> <p>

University of Oxford members should apply via <a href=’http://weblearn.ox.ac.uk/ses/”> http://weblearn.ox.ac.uk/ses/</a>, non-University members should apply via <a href=’mailto:courseinfo@xxx.ox.ac.uk’> courseinfo@xxx.ox.ac.uk</a>.</p></div>

</applicationProcedure>

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

This would be constructed using 2 parameters ${memberApplyTo} and ${publicApplyTo}:

<applicationProcedure><div xmlns="http://www.w3.org/1999/xhtml"> <p>

University of Oxford members should apply via <a href=’${memberApplyTo}’> ${memberApplyTo}</a>, non-University members should apply via <a href=’ ${publicApplyTo}’> ${publicApplyTo}</a>.</p>

</div></applicationProcedure>

Rationale: People can apply for some courses via WebLearn (& ITLP) but only if they are members of the University (as they have to log in). This means we must always have a second address where the public can apply, however, Oxford members may also see the 'public' feed on a departmental website, and should therefore be able to see the oxcap:memberApplyTo URI. This is why we need to cobble together text for the applicationProcedure field so that both application methods are always visible.

If the public are not allowed on a course, ie (16) Prerequistes is set to ST or OX, then the following XML should be used:

<applicationProcedure>University of Oxford members should apply via <a href=’${memberApplyTo}’> ${memberApplyTo}</a>, non-University members are not eligible to apply.

</applicationProcedure>

(10) (J) Start (XML: catalog >> provider >> course >> presentation >> start | dtf attribute) - an ISO 8601 date if an exact date is known, leave blank for an unknown date. Note that this is the date of the course NOT the time that the (first) session is to be held – session data is given separately.

(11) (K) Start text (XML: catalog >> provider >> course >> presentation >> start) - if start date is unknown then insert some useful text, eg, "To be confirmed" or “Middle of Michaelmas term” or “Upon demand”, otherwise add something that makes sense to a human reader – please try to make sure it doesn’t contradict the ISO date!

(12) (L) Venue (XML: catalog >> provider >> course >> presentation >> venue) - OxPoints ID or Plan On code of venue: http://oxpoints.oucs.ox.ac.uk/id/59444038 gives the location of the JR site (but not specific building). Please contact us if this is a problem. If there is a preference to withhold the specific location, please provide a more generic one.

Venue OxPoints IDCareers Service 23233545Careers Service Res Centre 23232676Language Centre 23233557OLI 23232618Safety Office Courses No set venue.JR (general) 59444038

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

Science area 23232331Churchill 23232654

(13) (M) Venue text (XML: catalog >> provider >> course >> presentation >> venue) – this is only necessary if ‘Venue’ cannot be supplied. Building (with optional room) is usually enough.

(14) (N) Status (XML: catalog >> provider >> course| oxcap:status attribute) & catalog >> provider >> course >> presentation | oxcap:status attribute) – One of “AC” (= Active) (or <blank>), “DC” (= Discontinued) or “CN” (= Cancelled). ‘Active’ is the default, if a course is not to be run again then the status (of the <course>) should be ‘Discontinued’ if a particular instance is withdrawn then use ‘Cancelled’ (in the <presentation> attribute). For DAISY this info needs to be communicated rather than just missing the course out of the export as we don’t delete an existing course in WebLearn.

Optional(15) (O) Learning Outcomes (XML: catalog >> provider >> course >> learningOutcomes) - up to

4000 characters which can be XHTML. This could be a list of keywords or subjects or topics or learning outcomes or objectives or some other brief synopsis.

(16) (P) Eligibility (XML: catalog >> provider >> course >> regulations | oxcap: eligibility attribute) - if the course is not open to everybody then please state the eligibility criteria. Use a 2 letter code: “OX” (= Oxford only) - default; “ST” (= Oxford staff only); “PU” (= Public). If there is nothing stated then the default is assumed. See: https://weblearn.ox.ac.uk/access/wiki/site/b1f728b0-0902-4666-869f 7993ca7d03d5/vocabularies.html

XML example

<regulations oxcap:eligibility=”ST”>Oxford staff only</regulations>

(17) (Q) Intended audience (XML: catalog >> provider >> course >> prerequisite | xsi:type=intendedAudience) – description of intended audience, should be about 60 characters and 10 words of plain text. It is highly recommended that this field is completed.

(18) (R) Subject (XML: catalog >> provider >> course >> subject) - use JACS code (see: https://weblearn.ox.ac.uk/access/content/group/b1f728b0-0902-4666-869f-7993ca7d03d5/Workshop%20Documentation/JACS3.pdf) As JISC consider this to be mandatory we need Oxford Open Data to automatically insert JACS codes where they are not supplied by the TP. This should be a text box on the Share Point data entry site.

One of Skills or Subject must be supplied.

We suggest the following JACS code for each training provider.

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

Training Provider JACS CodeOUCS (ITLP) Hopefully these can be mapped based on

other tags such as OxRDF (Research methods)

Careers L550OLI Not needed as no student courses?Language Centre T612 Arabic

T110 ChineseR110 FrenchR210 GermanR310 ItalianT210 JapaneseR711 RussianR410 Spanish

Cont. Ed. Already assigned codesLibraries P100 Information services (others??)MPLS Hopefully these can be mapped based on

other tags such as OxRDF (Research methods) and Skill categories.

Social Sciences dittoHumanities dittoMedical Sciences Hopefully these can be mapped based on

other tags such as OxRDF (Research methods)

Safety Office N620 – Health and Safety IssuesHRIS Not needed as no student courses?

(19) (S) Skills (XML: catalog >> provider >> course >> subject) – use a space or comma separated list of two letter Oxford ‘OxRDF’ categories (see Appendix A). This will map to a second ‘subject’ element in the XCRI-CAP feeds. This element will use our own OxRDF vocabulary.

One of Skills or Subject really should be supplied, if neither are present then we should use the title of the course as the subject.

XML example

<dc:subject identifier="PS" xsi:type="ox-rdf:notation" xmlns:ox-rdf="https://data.ox.ac.uk/id/ox-rdf/"> Presentation Skills</dc:subject>

Or

<catalog xmlns="something" xmlns:ox-rdf="https://data.ox.ac.uk/id/ox-rdf/" …> … <dc:subject identifier="PS" xsi:type="ox-rdf:notation"> Presentation Skills </dc:subject>…

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

</catalog>

The following ‘parent category’ should also be included:

<dc:subject identifier="GT" xsi:type="ox-rdf:notation" xmlns:ox-rdf="https://data.ox.ac.uk/id/ox-rdf/"> Graduate Training</dc:subject>

(20) (T) Research Methods (Skills) (XML: catalog >> provider >> course >> subject) – “QL” ( = Qualitative ) and / or “QN” ( = Quantitative) or leave blank if not applicable. This will generally only be set if the OxRDF category “SR” Study and Research Skills has been set in the previous column.

XML example

<dc:subject identifier="QL" xsi:type="ox-rm:notation" > xmlns:ox-rm="https://data.ox.ac.uk/id/ox-rm/"> Qualitative</dc:subject>

(21) (U) Description (XML: catalog >> provider >> course >> description) - can be XHTML. Less than 4000 characters in total. Course descriptions should be about 700 characters and 80 words.

You should include a general statement about what the course covers and the format what pre-course level of skill / knowledge is required and/or, where appropriate, an

indication of who the course is NOT suitable for details of anyone for whom this course is particularly recommended. For example is

it particularly useful for those working in particular subjects? Is it useful as a follow-up to another course, or is there another course that would follow this one usefully?

Other attributes including: course level, testimonials, format, any software used, course materials, course accreditation, assessments, teaching methods, and information relating to 'Where next?'

If the description is HTML then the text should be enclosed within:

<div xmlns="http://www.w3.org/1999/xhtml"> …

</div>

DAISY should output plain text descriptions, ie do not insert any tags.

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

(22) (V) URL (XML: catalog >> provider >> course >> URL) - a URL which gives more information, such as a web page about the course. This may or may not be the same URL as ‘Apply To’.

(23) (W) Booking Opens (XML: catalog >> provider >> course >> presentation >> applyFrom | dtf attribute) - ISO 8601 date specifying the date when booking opens

(24) (X) Booking Opens Text (XML: catalog >> provider >> course >> presentation >> applyFrom) – textual description of when booking opens, eg, “Week 1 MT2013”, “Start of Long Vac”

(25) (Y) Booking Closes Date (XML: catalog >> provider >> course >> presentation >> applyUntil | dtf attribute) - ISO 8601 date specifying the date when booking closes

(26) (Z) Booking Closes Text (XML: catalog >> provider >> course >> presentation >> applyUntil) – textual description of when booking opens, eg, “Week 5 MT2013”, “End of July”

(27) (AA) Attendance Mode (XML: catalog >> provider >> course >> presentation >> attendanceMode) - a 2 letter code: one of "CM" ( = Campus); "DA" ( = Distance with attendance); "DS" ( = Distance without attendance); "NC" ( = Face-to-face non-campus); "MM" ( = Mixed mode); "ON" ( = Online (no attendance)); "WB " ( = Work-based). Should be a drop down list in Share Point.

(28) (AB) Attendance Pattern (XML: catalog >> provider >> course >> presentation >> attendancePattern) - a 2 letter code: one of "DT"(= Daytime); "EV" (= Evening); "TW" (= Twilight); "DR" (= Day/Block release); "WE" (= Weekend); "CS" (= Customised); [I assume evening means 5pm / 6pm start and twilight is 7pm / 8pm / 9 pm start?] Should be a drop down list in Share Point.

(29) (AC) End (XML: catalog >> provider >> course >> presentation >> end | dtf attribute) - ISO 8601 date saying when course finishes. Note that this is the date of the end of the course NOT the time that the (first) session ends – session data is given separately.

(30) (AD) Places (XML: catalog >> provider >> course >> presentation >> places) – number of spaces (and be a textual description). Should be numeric field in Share Point (if there is such a thing.)

Optional Session Data

Some training providers would like to include info about their sessions. If this is the case then each row of a CSV file should be repeated and should just differ in these last 4 columns.

For XML files this info should be contained within the presentation in one or more <oxcap:session> elements. XML example

<oxcap:session>

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

<dc:identifier>Unique session ID string</dc:identifier> <mlo:start dtf=”..”> <end dtf=”..”> <venue>…..</oxcap:session><oxcap:session> ……..

(31) (AE) Session ID – session identifier, it would be sensible to simply enumerate each session starting from 1

(32) (AF) Date – date of session in ISO8601 format.

(33) (AG) Start time – start time of session in ISO8601 format.

(34) (AH) End time – end time of session in ISO8601 format.

(35) (AI) Venue – as above, if this is absent then it will be inherited from above (ie, from the surrounding <presentation>), this gives an opportunity to state different venues for the individual sessions.

(36) (AJ) Venue text – as above

Optional Qualification Data(37) Qualifications – at the moment we do not consider qualification to be necessary

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

Appendix A

There is a parent category to all these skills “Graduate Training” identified by the code “GT”.

RDS Domain GAP Category CodeMapped RDS Sub domains: knowledge, behaviour, attitude descriptors

RDS Subdomains

A: Knowledge and Personal Abilities

Computing CO Information literacy and management

A1: Knowledge Base

DA AnalysingSynthesising A2: Cognitive Abilities

Critical ThinkingEvaluating

Data Analysis Problem Solving

DM Research Methods – theoretical knowledge

A1: Knowledge BaseC1: Professional Conduct

Research Methods – practical application

Data Management

Information and literacy management

FW Subject knowledgeResearch methods A1: Knowledge Base

Field Work Information seekingRD Subject knowledge A1: Knowledge Base

A2: Cognitive AbilitiesA3: Creativity

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

Academic literacy and numeracyAnalysingSynthesisingCritical ThinkingEvaluatingInquiring mindIntellectual insightArgument constructionIntellectual risk

General Researcher Development

Research methods

IN Information seekingA1: Knowledge Base

Information Skills

Information literacy and management

LS Research methods: theoretical methods

A1: Knowledge BaseC1: Professional Conduct

Laboratory skills

Research methods: practical application

LA LanguagesA1: Knowledge Base

Languages Academic literacy and numeracyMM Problem Solving

Inquiring mindA2: Cognitive AbilitiesA3: Creativity

Argument ConstructionMathematical Intellectual risk

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

Methods

RM Research Methods – theoretical methods

A1: Knowledge Base

Research Methods

Research Methods – practical application

ST Research Methods – practical applicationResearch Methods

Information SeekingA1: Knowledge Base

Information literacy and management

Statistics Academic literacy and numeracy

Technical skills TE Research methods – practical application

A1: Knowledge Base

Study and Research Skills SR

Critical ThinkingEvaluatingProblem SolvingAcademic Literacy and NumeracyInformation Seeking

A1: Knowledge Base

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

RDS Domain GAP CategoryMapped RDS Sub domains: knowledge, behaviour, attitude descriptors

B: Personal Effectiveness

CD Career Management

Career Development

Continuing Professional Development

B3: Professional and Career Development

Responsiveness to opportunitiesNetworkingReputation and esteem

PE EnthusiasmPerseveranceIntegritySelf-confidenceResponsibilityPreparation and prioritisationTime ManagementResponsiveness to changeWork-life balance

B1: Personal QualitiesB2: Self ManagementPersonal

Effectiveness

Presentation Skills* PS Self-confidence

B1: Personal QualitiesD2: Communication and DisseminationD3: Engagement and Impact

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

RDS Domain GAP CategoryMapped RDS Sub domains: knowledge, behaviour, attitude descriptors

C:Research Governance and organisation

ETC1: Professional Conduct

Ethics Ethics and principles and sustainability

IP Ethics and principles and sustainability

C1: Professional Conduct

Legal requirementsIPR and CopyrightRespect and confidentialityAttribution and co-authorship

Intellectual property skills Appropriate practice

IL CollegialityTeam workingPeople Management D1: Working with Others

SupervisionMentoringInfluence and leadershipCollaboration

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

Interpersonal skills Equality and diversity

RF Research StrategyProject planning and deliveryRisk managementIncome and funding generationFinancial ManagementInfrastructure and resources

C3: Finance, Funding and Resources

Research and financial management

C1: Professional Conduct

Safety HS Health and Safety

RDS Domain GAP CategoryMapped RDS Sub domains: knowledge, behaviour, attitude descriptors

D: Engagement, Influence and impact

CS Communication methodsD2: Communication and DisseminationD3: Engagement and Impact

Communication mediaPublicationPublic engagement

Communication skills Teaching

EE EnterprisePolicy D3: Engagement and Impact

Society and CultureEnterprise and Entrepreneurs

Global Citizenship

Version 1.2

Authors: Adam Marshall, Bridget Taylor & Paull Hammond-Davies

hipCommunication methods

Communication mediaB1: Personal QualitiesD2: Communication and DisseminationD3: Engagement and Impact

Presentation skills* PS Teaching

SC Influence and leadership

Self-confidenceD1: Working with OthersD3: Engagement and Impact

Communication methodsCommunication media

Seminars / Colloquia Public Engagement

TA Communication methodsD2: Communication and DisseminationD3: Engagement and Impact

Communication mediaTeaching & Academic skills

Teaching

NB: *Please note presentation skills appears twice as it falls into two domains. However, we only require it to appear once!

Version 1.2