CO 6.1 As a Dept Administrator, I want to Create a New Course Offering by Copying in its entirety a Course Offering from an existing term. (KSENROLL-1927)

[KSENROLL-1932] Create back end functionality for Copy Course Offering from an existing term (except configure section) Created: 24/Jul/12  Updated: 13/Sep/12  Resolved: 15/Aug/12

Status: Closed
Project: KS Enrollment
Component/s: PDT - Green
Affects Version/s: M3
Fix Version/s: M4, M4 - Sprint 1
Security Level: Public (Public: Anyone can view)

Type: Sub Task Priority: Major
Reporter: Cassy Beekman (Inactive) Assignee: Venkat PremChandran (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relate
relates to KSENROLL-1933 Create user interface for Copy Course... Closed
relates to KSENROLL-1972 Create back end functionality for Con... Closed
relates to KSENROLL-1981 Create back end functionality for Cop... Closed
relates to KSENROLL-1993 Create back end functionality for Con... Closed
Rely
relies on KSENROLL-1943 Change service contracts for new Cour... Closed
relies on KSENROLL-2009 add copyCourseOffering Closed
KS ENR Functional Area: Course Offering

 Description   

See wireframe 05b
https://wiki.kuali.org/pages/viewpage.action?pageId=314935030

This Jira relates to creating the back end functionality for all elements of this page, except for the "Configure Course Offering Copy", which is covered in a different user story (6.2)(Jira 1928)



 Comments   
Comment by Cassy Beekman (Inactive) [ 26/Jul/12 ]

Please note that this Jira relies on 1943, which cannot be completed until the service branch merge is complete.

Comment by Venkat PremChandran (Inactive) [ 27/Jul/12 ]

For now, implemented the copy logic in CourseOfferingController, which we can move to services side (KSENROLL-2009)

Comment by Venkat PremChandran (Inactive) [ 06/Aug/12 ]

Implemented and it should generate unique COC on each copy. Now, it uses rolloverCourseOffering service method.

Pending - The list of results will be constrained via configuration of how many years to include in the search. I think it should not be a xml configuration. Looks like we can use parameter service

Comment by Venkat PremChandran (Inactive) [ 07/Aug/12 ]

Had discussion with Larry and it looks like we dont have a strategy to use ParameterService. Once we have a strategy, we can refactor. For now, I'm going to hardcode to display last 4 years COs and going to create a seperate jira to deal with configuration implementation

Comment by Cassy Beekman (Inactive) [ 08/Aug/12 ]

Thanks for investigating that, Venkat!

Comment by Venkat PremChandran (Inactive) [ 09/Aug/12 ]

Shall we create a seperate jira for displaying last 5 years CO. For this jira, i htink we're done with the copy functionality

Comment by Cassy Beekman (Inactive) [ 14/Aug/12 ]

I think that showing only the past 5 years of COs is part of the acceptance criteria, so that should be part of this jira. (Steve confirms it should be 5).

Comment by Venkat PremChandran (Inactive) [ 15/Aug/12 ]

implemented displaying last 5 (configurable in xml) years COs.

Comment by Venkat PremChandran (Inactive) [ 17/Aug/12 ]

I think I missed this part. Should we display only the offered COs or just all the COs for the last 5 years?

Comment by Taryn Pedigo (Inactive) [ 17/Aug/12 ]

Display the OFFERED COs for the last 5 years.

Comment by Cassy Beekman (Inactive) [ 20/Aug/12 ]

Sent jira 1933 to QA . Will close this one when 1933 passes.

Generated at Fri Mar 05 04:45:35 CST 2021 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.