...
To accomplish this we'd like to have the courses portlet DAO code split into a separate module so it can be included in other portlets to access course-related information. https://issues.jasig.org/browse/COURSESPLT-10
Course Details updated Data Model
UW-Madison is looking to add more details to the Course Details page. This will require additional data elements. The question is how should these additional data elements be added to the Data Model. Should there be more or less Structured Data in the Data Model. The move is to be toward keeping the Data Model as Generic ans Simple as possible so it is easier for more organizations to make use of the Data Model and the Courses Portlet.
UW-Madison specific data updates
UW-Madison tracks Courses (think of a factory), as well as Classes (think of an instance of a Course for a specific point in time such as Spring 2013). UW-Madison also tracks information associated with both Courses and Classes. In order to do this additional data elements will need to be added to the data model. The first cut at the Data Model xsd is to add the new data elements as structured data items. The thought is this will show what additional data elements are needed first. Then, upon examination, a more generic approach can be explored.
Added a simple type with enumerations to the Course Meeting definition in the commons.xsd to differentiate between a CLASS meeting and FINAL EXAM meeting.
Added a host of information to the courses.xsd file to represent the Class-level identifiers and Resources. Resources are basically URLs very similar to Course Updates but of a more permanent nature.