Top of Proposals

Index

Table of Contents

Feedback

Proposal Publication Processing

Publication Type
Publication Types defined in PAAW0600 may be used to collect sets of information about courses, units or unit sets.
e.g. A Publication Type of SCIENCE COURSE HANDBOOK could be defined to capture existing courses and approved course proposals belonging to the Science faculty.

Example
You wish to produce a handbook that includes details from a) all active Bachelor degree Courses and new course proposals that haven’t been transferred and b) existing units which have offerings in 2012 and c) some information defined in user defined proposals titled HANDBOOK and OVERVIEW.

Create Publication Type record and:

a) In PAAW0600, select Course details for inclusion.

b) In PAAW0600, select Unit details for inclusion.

c) In PAAW0600, select Userdef details for inclusion.

At some point during data entry, the Stylesheet details must be recorded in the Stylesheet text box. One stylesheet is recorded for the publication type. This is text in the format of an XSLT file that determines the contents and format to be used in the publication.

Web Service
With the Publication Type defined, the user can then call the publicationProposal web service.
This web service enables the publications data to be extracted.

Input parameters for the web service are:
Publication Type - Name of the publication Type as defined in PAAW0600.
Extract Date - May affect the Publication Type / system Proposal Type records extracted according to their Start and End Dates recorded in PAAW0600.
Approved Data only? - Yes if only data from approved proposals are to be included
System Proposal type - Nominate if limiting to only one system proposal type
Proposal ID -Nominate if limiting to only one proposal id
Context - Nominate if limiting to only one course, unit or unit set version.

Proposals whose data is to be included
The web service looks at the Publication Type and identifies the System Proposal Types to be extracted. Only system proposal types where the extract date (input parameter for web service) is between the start and end date defined in the publication type will be extracted.
Proposals may be included if the BOTH or PROPOSAL selection Option is selected. The range of Proposals included in the extract will be determined by the Proposal Type selected for each System Proposal Type. In the example above, the COURSE System Proposal Types does not have a Proposal Type assigned, so course data from all proposals that satisfy the selection criteria will be included in the extract. (i.e. In this example, where a new course is the proposal outcome but the proposal data hasn’t been transferred into CRS).
Publications for COURSEs, UNITs or UNIT-SETs may exist in Callista CRS or in proposals, however USERDEFs only exist as proposals. A proposal type can be selected for the USERDEF Proposal Type and selection criteria recorded but only for proposals.

The extract may be run for proposals that have not yet been approved or for approved data only, according to the ‘Approved Data only?’ input parameter for the web service. Where it is run for 'Only Approved Data', only data from the latest approved proposal instance will be included in the extract.

Courses, Unit Sets and Units whose data is to be included
COURSEs, UNITs or UNIT-SET data in CRS may be extracted for Publications if the BOTH or CONTEXT(COURSES, UNIT SETS or UNITS) Selection Option is selected.

In the example above, the COURSE System Proposal Types does not have a Proposal Type assigned, so course data from all proposals that satisfy the selection criteria will be included in the extract. (i.e. In this example, for Bachelor degree courses).
Then, when the publication extract is run for the publication type, it will only extract the CRS Course data that meets this selection criterion.

What data from each?
For USERDEF System Proposal Types, the Proposal Type selected in the Publication Type field will define the set of USERDEF data extracted.
For other System Proposal Types, the process extracts either the data for the Definitive Instance Proposal Type for the system proposal type or the Proposal Type when selected for the System Proposal Type on this page. This is determined by whether YES or NO is selected for the 'Use Definitive Instance' field.
In the example above, because Use Definitive Instance = YES for the COURSE and UNIT System Proposal Types, the set a data included in each case will be defined by the Proposal Type defined in PAAW0200 as the Definitive Type for the COURSE and UNIT System Proposal Types.
For the USER-DEF system the function will utilise the proposal type recorded in the publication type definition (Proposal id 587).

Stylesheet
The content and look of the information is defined here by the Stylesheet entry. That entry must be in the form of an XML stylesheet, which is used by the webservice to determine which fields are included in the extracted data. The stylesheet also determines the style and order of the fields.

Last modified on 1 June, 2012 1:22 PM

History Information