Student Roster Changes

[LA2425]

Hello,

Can you please clarify the expected behavior for the following scenarios with regard to a published Evaluation Portfolio:

• If an attached course has student roster changes during the course, will the roster changes reflect the same access to the portfolio? In other words, if I am a student that is enrolled in a course mid-semester and my class is using this porftolio, will I also be able to use it?
• If an attached course is the parent course to a different section I crosslist to it, will the students in the child course be able to access the portfolio? In other words, if the portfolio is attached to Class A and published, but later I crosslist Class B to the course, do Class B students get access to the portfolio?
  • Does this answer change based on where the child course is in an active vs future term when crosslisted to the parent course?

Thanks!

[p_a_hudson]

In my testing, I'm not seeing changes to a class list reflected in an assigned portfolio. For our use, this has to be fixed, otherwise the portfolio can't be used until pretty much the end of a course. We regularly have students change modules up to a month after a module has started teaching. If you want to use the portfolio as a reflection tool to capture progress, you would be releasing the evaluation portfolio at the start of teaching. So there has to be some kind of sync. 

There are two fundamental issues with the way Portfolios seem to be implemented, which should have been part of the design brief for any beta release.

• If the Portfolio option is enabled as an LTI within a module. It should show portfolios allocated to that module and any member of the module clicking into the portfolio section should be automatically allocated to any connected evaluation portfolios. Tutors should see the portfolio created by other teaching staff and be given edit and review rights, and students who weren't originally registered, automatically provisioned when the LTI is opened. 
• There should also be a regular sync between Portfolio and Canvas via the APIs to keep the class list in sync with the module so that staff can monitor none completion.

For me, a sync'd class list is a basic requirement.