Nabble - Sakai - Portfolio

[Portfolio] Report Out > Sakai Teaching and Learning Group Update

2009-12-08T10:33:24Z

Folks,

I wanted to take a moment to report out to the lists from the Teaching and Learning group call from last week (sorry for the delay).

Last week Clay Fenlason, Sakai Product Manager, joined the Teaching and Learning call to discuss the work that has been going on in the Learning Capabilities Google spreadsheet and how this work has already started to be used in Sakai 3 design efforts. A good recap of this initial design work as well as some reference materials can be found on Clay's blog at: http://sakaipm.wordpress.com/ (see the Leading Design posting as well as his most recent that followed the call).

Based on this discussion, the T&L group (which includes good representation from the UX and OSP groups!) felt that the next step in this process needs to be an effort to categorize the existing Learning Capabilities (which number over 110 now) and look for gaps that we want to fill in. The exact process for how to best do this is unclear but will be the topic of the next couple of calls. List discussions on this are also encouraged. Tentatively, the group is contemplating holding a "virtual meeting" of 1-2 days sometime in early January during which the "categorization" would be worked on.

Finally, we would like to encourage the community to spend time over the next 2-3 weeks looking at and contributing to the Learning Capabilities spreadsheet (a link can be found at http://confluence.sakaiproject.org/display/PED). Although if a capability does not get documented at this point it DOES NOT mean that it won't be in Sakai 3, by documenting them now we will have greater influence over the initial design efforts.

Again, apologies for the delay in getting this reported out to the community.

Josh

-----------------------------
Joshua Baron
Director, Academic Technology and eLearning
Marist College
Poughkeepsie, New York 12601
(845) 575-3623 (work)
Twitter: JoshBaron
_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] [DG: User Experience] [DG: Teaching & Learning] Leading Design

2009-12-03T11:23:09Z

It's good to hear about all this, Keli. It might have been ideal if we'd had your work in hand when Sam started, but there's plenty of room for it to still be helpful. The target of the current phase is not to produce robust support for a wide variety of learning activities, but rather to distill an essential and fundamental interaction pattern that can be built upon. In other words, a core activity that can flex to eventually satisfy more complex cases.

So it seems to me one helpful way to use your work over the near term would be to use it to exercise what has been produced thus far: take the themes and activities gleaned from your interviews - the ones dealing with submission-feedback loops of all sorts - and work through some wireframes or paper prototypes with them. Look for points where their simple interactions could branch, or where they might look too brittle to accommodate the need. You might also point out themes you've identified that don't seem to be included, assuming they belong in that scope.

Which of course means we need to get these wireframes/prototypes into your hands. I'm hopeful they will have settled down well enough in the next week, and maybe a few of us could get together and go over them.

~Clay

On Thu, Dec 3, 2009 at 1:49 PM, <kamann@...> wrote:

Hi Clay,
As you know, this fall, Stanford embarked on the learning activities investigation with 8 other schools it was because we were concerned about two things—1) how learning activities, especially problem sets and tests, were created, taken and evaluated 2) identifying commonalities between how various types of activities (including papers, projects, and posts) were assigned by instructors and how activities and feedback was received by students. Part 2 was important because we wanted to insure that instructors and students no longer had to go to 2-3 different pages depending on the type of activity they were working with.

Thus our scope was widened to all "learning activities"--It was not clear who would build that framework or when, such as a unified dashboard view for instructors and students, but we wanted to help inform such a united framework that cut across "tool silos" before we designed and developed problem sets and tests.

In the meantime, Georgia Tech and Cambridge, along with the Sakai Foundation, hired Sam to design a simple course template in preparation for their adoption of Sakai 3 next summer. I knew this included syllabus building and viewing, but I'll admit, that until Clay mentioned the PDF posted on his blog at the t&l call yesterday, I was not aware that it would also include electronic submission and evaluation of assignments, specifically file uploads of papers (had not followed the link from his email before thanksgiving to http://sakaipm.wordpress.com/2009/11/19/leading-design/).

Yesterday, I reviewed Sam's work with much interest. As we are nearing the end of the learning activities interviews, I am happy to see that these sketches already address some major things we've been hearing.

I am hoping that our findings will be useful, both in giving supporting to design decisions as well as in suggesting adjustments. It will certainly be useful helping to map out future elaboration that might be required for assigning other types of activities. After our check in yesterday, we know we have 21 interviews from 7 schools (Texas, Berkeley, Michigan, Indiana, Virginia Tech, Wyoming, and Stanford) and I believe there will be more if Mt. Holyoke and Marist decide to proceed. Two of the schools provided 6 interviews about instructors who had their students turning in written work. We have 13 interviews about problem sets or quizzes. We also have 7 instructors who described at least 4 additional types of activities. The four student interviews we have give some additional insight.

Our original plan was to produce a write up, including personas and major themes, by the end of January. However, I did want to check in to see if there were other things we might do in light of Sam's work. Many have been asking if we were contributing to the spreadsheet and if this is continuing to drive his work, it might be worth it, but perhaps direct feedback on the design would be more useful at this stage.

Best,

Keli Amann
User Experience Specialist
Academic Computing, Stanford University

----- Original Message -----

From: "David Goodrum" <davidgoodrum@...>
To: adevans@..., "Sakai UX" <sakai-ux@...>, "pedagogy Learning" <pedagogy@...>, portfolio@...
Sent: Tuesday, December 1, 2009 7:13:17 AM GMT -08:00 US/Canada Pacific
Subject: Re: [DG: User Experience] [DG: Teaching & Learning] Leading Design

Hi Amber,

I'm encouraged to hear that some of what you have found in your contextual inquiry is already hinted at in the Learning Capabilities spreadsheet. It makes me more optimistic that these different kinds of efforts will dovetail and build on each other as the community pushes forward towards a deep understanding of how Sakai 3 needs to support teaching and learning. Any of the themes and activity flows emerging in the spreadsheet would benefit from the kind of deeper understanding that comes from contextual inquiry. I'm anxiously looking forward to the sharing that Keli Amann in a recent message said would happen by the end of January. Recently, Janice Smith has added concepts to the spreadsheet that reflect work the Portfolio community has done. There were hints in the spreadsheet already about portfolio-like capabilities, but the spreadsheet is much improved by the thorough treatment of these ideas directly from the Portfolio community. I think the rewards for finding and maintaining these broad connections between various teaching and learning concepts will be a rich set of Sakai 3 services available anywhere in the system and not just tied to specific tools or views.

Regards - David Goodrum

Director, Academic and Faculty Services
Learning Technologies
University Information Technology Services
Indiana University

From: Amber D. Evans <adevans@...>
To: Sakai UX <sakai-ux@...>
Sent: Mon, November 30, 2009 3:11:22 PM
Subject: Re: [DG: User Experience] [DG: Teaching & Learning] Leading Design

Clay,

(I'm reposting this to the larger Sakai community at your request.)

I hope that I and my group are not tragically late to this game, as we've been working with Stanford on collecting interviews as part of their Assignments and Test & Quizzes Contextual Inquiry/Fluid research design. My 3 person team and I will be spending much of today and Tuesday compiling our user persona notes form those interviews. I know that many other schools are also contributing to the Stanford UX project and may have similar questions or capability to contribute to the larger T&L Sakai 3.0 capabilities. Once done, my team and I would like to share resulting composite persona info with your group (and we have already started adding a little bit to the Google document ).

We just wanted to make sure that we didn't entirely miss the boat on this one, since the timeline is not entirely clear as to when this kind of user data will no longer be needed ... as your blog posting indicates , it's a constant on-going project, but I also recognize that at some point things have to be settled in order to move forward. We have noticed that much of what we could contribute has already been identified in the list, and only a few more ideas of value may be added (from us). If you could let me know how my colleagues and I can best make learning capabilities contributions (or other things) at this stage, it would be appreciated. Thanks!

Sincerely,
Amber D. Evans

Training and Documentation Coordinator, Online Course Systems (OCS)
= = =
Learning Technologies, Virginia Tech, 1220B Torgersen Hall (0292), Blacksburg, VA 24061
540.231.8053 | adevans@... | http://amsdiane.blogspot.com/
= = =
"Non scholae sed vitae discimus" ("We learn not for school but for life") -Seneca

On Mon, Nov 23, 2009 at 7:03 PM, David Goodrum < davidgoodrum@... > wrote:

It's been interesting to see the level of collaboration the document has seen and how it has evolved because of that collaboration.

According to Google docs, there's been at least 15 collaborators on the document... likely more, since no login is required to edit it -- it is a totally open brainstorming document right now.

The spreadsheet is certainly not exhaustive nor complete, nor is that the intent for this phase. It currently does not necessarily reflect the best capabilities of Sakai 2.x; it does not reflect what all is missing or frustrating about Sakai 2.x; it does not reflect all of what Sakai 3 should aspire to; it doesn't even fully represent what teaching and learning goals should be supported in Sakai 3. So what's the point?

With 60+ rows right now, it begins to represent a fair cross section of many ambitions Sakai 3 perhaps ought to have in the teaching and learning space.

And it attempts to show how different levels of complexity and functional capabilities both link together and link back to a basic teaching and learning goal, hopefully expressed in everyday language.

Perhaps a bad analogy for the document would be the recent cell coverage maps... Ideally, our teaching and learning map would look like Verizon's 3G map... with nearly the whole map filled in. This brainstorming document today is more like the AT&T 3G coverage map: a lot of white space still to be filled in, but there is coverage of many core areas and outlines of many others.

For now it's a place to play out some ideas.

Got a teaching and learning idea? Something instructors want their students to do? Something students wish instructors would do? Something that develops collaboration and cooperation among students, encourages active learning, gives prompt feedback, emphasizes time on task, communicates high expectations, or respects diverse talents and ways of learning? Then add it to the brainstorm.

- David

From: Clay Fenlason < clay.fenlason@... >
To: Sakai UX < sakai-ux@... >; pedagogy Learning < pedagogy@... >
Sent: Wed, November 18, 2009 7:28:43 PM
Subject: [DG: User Experience] Leading Design

In recent weeks I've been trying to promote the maturation of the
learning capabilities spreadsheet [1] that David Goodrum has
championed. At the same time I've heard concerns that it might come to
naught or not be listened to. Just a couple days ago Josh Baron was
asking me when and how I thought the spreadsheet might actually be
used to inform the design. I told him, "It's happening right now." I'm
not sure he believed me, so I made a blog post with evidence:
http://sakaipm.wordpress.com

~Clay

[1] https://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en
_______________________________________________
sakai-ux mailing list
sakai-ux@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-ux

TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"

_______________________________________________
pedagogy mailing list
pedagogy@...
http://collab.sakaiproject.org/mailman/listinfo/pedagogy

TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe"

_______________________________________________
sakai-ux mailing list
sakai-ux@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-ux

TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

[Portfolio] Reminder > Sakai Teaching and Learning Call TODAY (with Clay Fenlason)

2009-12-02T07:38:18Z

Folks,

We will be having our regular weekly Teaching and Learning Sakai group call today at 12 Noon EST. Call-in information is below.

As a reminder, the group has spent the past month or so working on populating the Learning Capabilities Google spreadsheet with simple user-centric goals. At the present time (thanks in part of the work of Janice Smith over the last week who added a lot of portfolio-focused goals), we have 113 rows of goals documented. The spreadsheet is linked off the Teaching and Learning confluence site.

The group decided previously that we would take a "pause" at this point in the population process to assess what we've created and discuss how to begin to organize and group what has been documented. As part of this effort, we have invited Clay Fenlason, Sakai Product Manager, to join the call again today so that we can engage in a discussion with him as to how the materials are currently being used and how they might be used in the future. This discussion should help inform our next round of activities.

To help prepare for our conversation with Clay, I would like to suggest that folks take a few minutes prior to the call to read over his recent blog posting (see the Leading Design post at http://sakaipm.wordpress.com) as it discusses how he had been using the materials to date and provides an example from Sam Peck, the designer he is working with, as well.

Talk with everyone in a bit,

Josh

Calls are currently taking place every Wednesday at 12:00 Noon ET (New York, USA). To participate:

* Dial 1-888-447-7153 (International callers: 1-719-387-1138)
* Enter in passcode: 917798 (the hit #)
* Listen to music until "moderator" starts the call
* Need help? Call tech support at 1-877-807-0970

-----------------------------
Joshua Baron
Director, Academic Technology and eLearning
Marist College
Poughkeepsie, New York 12601
(845) 575-3623 (work)
Twitter: JoshBaron
_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] Access to portfolios beyond graduation - Matrix tool export?

2009-12-01T07:51:51Z

Here's one place to share this requirement:

The Teaching and Learning spreadsheet, as elaborated by Janice Smith
with goals relating to portfolio work, contains this very request on
line 97, Simple Goal "Download any portfolio one owns for use outside
the system." I have added a notation to the Alternative Goal column
referring to SAK-6069. See also line 95, "Access any item one owns or
has permission to access as long as one has an account in the system."

The Confluence Teaching and Learning page gives a link to the
spreadsheet, and the Portfolio Vignettes page gathers the fundamental
portfolio requirements.

Jim Doherty wrote:

> Hello Nancy, Beth, Portfolio folk,
>
> We've got a similar requirement - access to matrix beyond graduation
> -- and some questions. I'm wondering if anyone has some more info or
> ideas to share.
>
> We've got a number of schools using the matrix tool intensively. At
> the moment there is no 'user export' of the matrix data. There is an
> export for coordinators to export/import matrix definitions, but the
> filled-in, in-use student matrix can not be exported as far as I
> know. I found a SAKAI JIRA for this requirement (SAK-6069
> <http://jira.sakaiproject.org/browse/SAK-6069>) but no recent info or
> activity.
>
> Some questions for the group:
>
> 1. Has anyone else the same requirement? How do you handle this
> today? screenprints? save web page? other? 2. I seem to remember
> seeing that matrix and other wizards could be -included- in
> 'portfolios'. Has anyone done this or could provide info on how this
> is done? Perhaps this would be an opportunity to meet both
> requirements, exporting user matrix and exporting portfolios, at the
> same time.
>
> We are also considering extending student access to the system beyond
> graduation until we can meet this requirement.
>
>
> best regards, Jim Doherty
>
> -- Jim Doherty Learning4u w: www.learning4u.nl
> <http://www.learning4u.nl> t: 0207163981 m: 06 48754913
>
>
>
> On Wed, Nov 18, 2009 at 10:42 PM, Nancy O'Laughlin <nolaug@...
> <mailto:nolaug@...>> wrote:
>
> We have had several requests from faculty to continue student
> portfolio access beyond graduation for viewing and editing. I was
> wondering how other institutions handle this. Could you let me know
> what policies you have in place or are considering? Are there any
> particular issues involved with giving extended access to students?
> Thanks, Nancy
>
> -- Nancy J. O'Laughlin, Ed.D. IT-Client Support & Services,
> University of Delaware 030 Smith Hall, 18 Amstel Avenue Newark, DE
> 19716 nolaug@... <mailto:nolaug@...> 302.831.0737
>
> _______________________________________________ portfolio mailing
> list portfolio@...
> <mailto:portfolio@...>
> http://collab.sakaiproject.org/mailman/listinfo/portfolio
>
> TO UNSUBSCRIBE: send email to
> portfolio-unsubscribe@...
> <mailto:portfolio-unsubscribe@...> with a subject
> of "unsubscribe"
>
>

--
Robin Hill, Ph.D. hill@... 307-766-5499
Instructional Computing Services http://www.uwyo.edu/ctl
Ellbogen Center for Teaching and Learning University of Wyoming

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] [DG: User Experience] [DG: Teaching & Learning] Leading Design

2009-12-01T07:13:17Z

Hi Amber,

I'm encouraged to hear that some of what you have found in your contextual inquiry is already hinted at in the Learning Capabilities spreadsheet. It makes me more optimistic that these different kinds of efforts will dovetail and build on each other as the community pushes forward towards a deep understanding of how Sakai 3 needs to support teaching and learning. Any of the themes and activity flows emerging in the spreadsheet would benefit from the kind of deeper understanding that comes from contextual inquiry. I'm anxiously looking forward to the sharing that Keli Amann in a recent message said would happen by the end of January. Recently, Janice Smith has added concepts to the spreadsheet that reflect work the Portfolio community has done. There were hints in the spreadsheet already about portfolio-like capabilities, but the spreadsheet is much improved by the thorough treatment of these ideas directly from the Portfolio community. I think the rewards for finding and maintaining these broad connections between various teaching and learning concepts will be a rich set of Sakai 3 services available anywhere in the system and not just tied to specific tools or views.

Regards - David Goodrum

Director, Academic and Faculty Services

Learning Technologies

University Information Technology Services

Indiana University

From: Amber D. Evans <adevans@...>
To: Sakai UX <sakai-ux@...>
Sent: Mon, November 30, 2009 3:11:22 PM
Subject: Re: [DG: User Experience] [DG: Teaching & Learning] Leading Design

Clay,

(I'm reposting this to the larger Sakai community at your request.)

I hope that I and my group are not tragically late to this game, as we've been working with Stanford on collecting interviews as part of their Assignments and Test & Quizzes Contextual Inquiry/Fluid research design. My 3 person team and I will be spending much of today and Tuesday compiling our user persona notes form those interviews. I know that many other schools are also contributing to the Stanford UX project and may have similar questions or capability to contribute to the larger T&L Sakai 3.0 capabilities. Once done, my team and I would like to share resulting composite persona info with your group (and we have already started adding a little bit to the Google document).

We just wanted to make sure that we didn't entirely miss the boat on this one, since the timeline is not entirely clear as to when this kind of user data will no longer be needed ... as your blog posting indicates, it's a constant on-going project, but I also recognize that at some point things have to be settled in order to move forward. We have noticed that much of what we could contribute has already been identified in the list, and only a few more ideas of value may be added (from us). If you could let me know how my colleagues and I can best make learning capabilities contributions (or other things) at this stage, it would be appreciated. Thanks!

Sincerely,
Amber D. Evans

Training and Documentation Coordinator, Online Course Systems (OCS)
= = =
Learning Technologies, Virginia Tech, 1220B Torgersen Hall (0292), Blacksburg, VA 24061
540.231.8053 | adevans@... | http://amsdiane.blogspot.com/
= = =
"Non scholae sed vitae discimus" ("We learn not for school but for life") -Seneca

On Mon, Nov 23, 2009 at 7:03 PM, David Goodrum <davidgoodrum@...> wrote:

It's been interesting to see the level of collaboration the document has seen and how it has evolved because of that collaboration.

According to Google docs, there's been at least 15 collaborators on the document... likely more, since no login is required to edit it -- it is a totally open brainstorming document right now.

The spreadsheet is certainly not exhaustive nor complete, nor is that the intent for this phase. It currently does not necessarily reflect the best capabilities of Sakai 2.x; it does not reflect what all is missing or frustrating about Sakai 2.x; it does not reflect all of what Sakai 3 should aspire to; it doesn't even fully represent what teaching and learning goals should be supported in Sakai 3. So what's the point?

With 60+ rows right now, it begins to represent a fair cross section of many ambitions Sakai 3 perhaps ought to have in the teaching and learning space.

And it attempts to show how different levels of complexity and functional capabilities both link together and link back to a basic teaching and learning goal, hopefully expressed in everyday language.

Perhaps a bad analogy for the document would be the recent cell coverage maps... Ideally, our teaching and learning map would look like Verizon's 3G map... with nearly the whole map filled in. This brainstorming document today is more like the AT&T 3G coverage map: a lot of white space still to be filled in, but there is coverage of many core areas and outlines of many others.

For now it's a place to play out some ideas.

Got a teaching and learning idea? Something instructors want their students to do? Something students wish instructors would do? Something that develops collaboration and cooperation among students, encourages active learning, gives prompt feedback, emphasizes time on task, communicates high expectations, or respects diverse talents and ways of learning? Then add it to the brainstorm.

- David

From: Clay Fenlason <clay.fenlason@...>
To: Sakai UX <sakai-ux@...>; pedagogy Learning <pedagogy@...>
Sent: Wed, November 18, 2009 7:28:43 PM
Subject: [DG: User Experience] Leading Design

In recent weeks I've been trying to promote the maturation of the
learning capabilities spreadsheet [1] that David Goodrum has
championed. At the same time I've heard concerns that it might come to
naught or not be listened to. Just a couple days ago Josh Baron was
asking me when and how I thought the spreadsheet might actually be
used to inform the design. I told him, "It's happening right now." I'm
not sure he believed me, so I made a blog post with evidence:
http://sakaipm.wordpress.com

~Clay

[1] https://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en
_______________________________________________
sakai-ux mailing list
sakai-ux@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-ux

TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"

_______________________________________________
pedagogy mailing list
pedagogy@...
http://collab.sakaiproject.org/mailman/listinfo/pedagogy

TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe"

[Portfolio] Fwd: [Building Sakai] OSP Production experience

2009-11-30T08:44:58Z

Forwarding this from production and dev lists.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

---------- Forwarded message ----------
From: Nuno Fernandes <nuno@...>
Date: Thu, Nov 26, 2009 at 4:25 AM
Subject: Re: [Building Sakai] OSP Production experience
To: production@...
Cc: sakai-dev <sakai-dev@...>

Re-arranging points based on Sean's comments! (Thank you Sean!)
Please don't interpret this as an survey - if you are able to answer
one of these points or add any other observation I would be very glad!

Sakai version used
overall OSP stability
any special properties settings used to address any eventual performance concern
"arrangement" of OSP tools
number of users in the portfolio sites
user experience/satisfaction
hardware resources overhead compared to a Sakai installation without OSP
estimated time on setup/configuration
relation of number employees for support per number of students (if it
makes sense)
(others you may find useful?)

Thank you very much,
Nuno

On Wed, Nov 25, 2009 at 3:14 PM, Sean Keesler
<sean.keesler@...> wrote:

>
> Nuno,
>
> You might be aware that OSP comes with a number of different tools that can be mixed and matched together for different purposes.
> You might ask for respondents to qualify their answers with:
> - their "arrangement" of tools
> - the version of Sakai they are running...wizards might chew through more system resources than matrices. Matrices with really large groups may use more system resources than a simple template based portfolio with just a couple content sources.
> - any special properties settings that they are using to address performance concerns
> - the number of users in the portfolio sites
>
> You might find some ruts in the road to avoid....or jump in!
>
> Sean Keesler
> 130 Academy Street
> Manlius, New York 13104 USA
> 315-663-7756
> sean.keesler@...
>
>
> On Wed, Nov 25, 2009 at 9:50 AM, Nuno Fernandes <nuno@...> wrote:
>>
>> Hi all,
>> Currently, we (UFP) are not using ePortfolios (OSP) in our production instance (UFP-UV), but we would like to have some feedback from the community before evaluating it for a distinct project we may participate on. Could you please share any production experience you have with Sakai OSP?
>> Together with any valuable information you may provide, I would like to konw you experience regarding:
>>
>> overall OSP stability
>> user experience/satisfaction
>> hardware resources overhead compared to a Sakai installation without OSP
>> estimated time on setup/configuration
>> relation of number employees for support per number of students (if it makes sense)
>> (others you may find useful?)
>>
>> Thank you very much,
>> Nuno
>> --
>> Nuno Fernandes
>>
>> Profile | http://facebook.com/nfgrilo | http://linkedin.com/in/nfgrilo
>> Web | http://codingwithcoffee.com | http://twitter.com/nfgrilo
>> Work | Analyst/Programmer @ UFP-UV [http://elearning.ufp.pt]
>> | Analyst/Programmer @ Sakai Foundation [http://sakaiproject.org]
>> | Sakai Fellow 2008 @ Sakai Foundation [http://confluence.sakaiproject.org//x/6oCTAQ]
>> Address | Universidade Fernando Pessoa [http://www.ufp.pt]
>> | Praça 9 de Abril, 349 | 4249-004 Porto
>> | tel: + 351 22 507 13 00 | fax: + 351 22 550 82 69
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev@...
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe@... with a subject of "unsubscribe"
>

--
Nuno Fernandes

Profile | http://facebook.com/nfgrilo | http://linkedin.com/in/nfgrilo
Web | http://codingwithcoffee.com | http://twitter.com/nfgrilo
Work | Analyst/Programmer @ UFP-UV [http://elearning.ufp.pt]
| Analyst/Programmer @ Sakai Foundation [http://sakaiproject.org]
| Sakai Fellow 2008 @ Sakai Foundation
[http://confluence.sakaiproject.org//x/6oCTAQ]
Address | Universidade Fernando Pessoa [http://www.ufp.pt]
| Praça 9 de Abril, 349 | 4249-004 Porto
| tel: + 351 22 507 13 00 | fax: + 351 22 550 82 69

_______________________________________________
sakai-dev mailing list
sakai-dev@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to
sakai-dev-unsubscribe@... with a subject of
"unsubscribe"
_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] portfolio Digest, Vol 9, Issue 31

2009-11-29T11:59:17Z

Thank you for contacting me. I am out of the office until November 30th and will get back to you then. Have a wonderful holiday!

Re: [Portfolio] portfolio Digest, Vol 9, Issue 30

2009-11-28T11:59:22Z

Thank you for contacting me. I am out of the office until November 30th and will get back to you then. Have a wonderful holiday!

Re: [Portfolio] portfolio Digest, Vol 9, Issue 29

2009-11-27T11:59:23Z

Thank you for contacting me. I am out of the office until November 30th and will get back to you then. Have a wonderful holiday!

Re: [Portfolio] Access to portfolios beyond graduation - Matrix tool export?

2009-11-27T03:27:24Z

Hello Nancy, Beth, Portfolio folk,

We've got a similar requirement - access to matrix beyond graduation -- and some questions. I'm wondering if anyone has some more info or ideas to share.

We've got a number of schools using the matrix tool intensively. At the moment there is no 'user export' of the matrix data. There is an export for coordinators to export/import matrix definitions, but the filled-in, in-use student matrix can not be exported as far as I know. I found a SAKAI JIRA for this requirement (SAK-6069) but no recent info or activity.

Some questions for the group:

1. Has anyone else the same requirement? How do you handle this today? screenprints? save web page? other?
2. I seem to remember seeing that matrix and other wizards could be -included- in 'portfolios'. Has anyone done this or could provide info on how this is done? Perhaps this would be an opportunity to meet both requirements, exporting user matrix and exporting portfolios, at the same time.

We are also considering extending student access to the system beyond graduation until we can meet this requirement.

best regards,
Jim Doherty

--
Jim Doherty
Learning4u
w: www.learning4u.nl
t: 0207163981
m: 06 48754913

On Wed, Nov 18, 2009 at 10:42 PM, Nancy O'Laughlin <nolaug@...> wrote:

We have had several requests from faculty to continue student portfolio
access beyond graduation for viewing and editing. I was wondering how
other institutions handle this. Could you let me know what policies you
have in place or are considering? Are there any particular issues
involved with giving extended access to students?
Thanks,
Nancy

--
Nancy J. O'Laughlin, Ed.D.
IT-Client Support & Services, University of Delaware
030 Smith Hall, 18 Amstel Avenue
Newark, DE 19716
nolaug@... 302.831.0737

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] portfolio Digest, Vol 9, Issue 28

2009-11-26T11:59:21Z

Thank you for contacting me. I am out of the office until November 30th and will get back to you then. Have a wonderful holiday!

Re: [Portfolio] portfolio Digest, Vol 9, Issue 27

2009-11-25T11:59:30Z

Thank you for contacting me. I am out of the office until November 30th and will get back to you then. Have a wonderful holiday!

Re: [Portfolio] [DG: Teaching & Learning] Portfolio capabilities added to Learning Capabilities spreadsheet

2009-11-25T05:42:44Z

Janice,
Great job. I'm not as creative as Erica - but thanks for all your work,
a lot of thought went into your entries.
Nancy

janice.smith wrote:

> Dear OSP and T&L Communities
>
> I have just finished a reorganization and rewriting of the
> Portfolio-related Vignettes from Sakai Confluence and have posted them
> on rows 74-98 on the Learning Capabilities Google Spreadsheet. The
> rewrite was necessary because the categories on our Confluence page
> are different from the categories on the Learning Capabilities
> spreadsheet. I attempted to fully preserve the intent of our original
> document.
>
> The Learning Capabilities spreadsheet can be found at
> http://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en
> <http://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en>.
>
>
> I invite comments and critiques from the OSP Community. (Please send
> them to me directly.) Let's make sure we tell our story well!
>
> T&L friends - we are hopeful that you will see how many similarities
> there are between the needs of users in our two communities. We look
> forward to continued collaboration on the functionality of Sakai 3.0!
>
> Janice
>
> Janice A. Smith, Ph.D.
> 2009 Sakai Foundation Fellow
> Three Canoes
> 1204 Laurel Avenue
> Saint Paul, Minnesota 55104, USA
> 651-642-9069, 207-841-6262 (cell)
> janice.smith@... <mailto:janice.smith@...>
> jasmith@... <mailto:jasmith@...>
> ------------------------------------------------------------------------
>
> _______________________________________________
> pedagogy mailing list
> pedagogy@...
> http://collab.sakaiproject.org/mailman/listinfo/pedagogy
>
> TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe"

--
Nancy J. O'Laughlin, Ed.D.
IT-Client Support & Services, University of Delaware
030 Smith Hall, 18 Amstel Avenue
Newark, DE 19716
nolaug@... 302.831.0737

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] Portfolio capabilities added to Learning Capabilities spreadsheet

2009-11-24T17:40:38Z

Jan,

You are a Hero of Soviet Labor, overfulfilling the norm once again.

Thanks,

Erica
________________________________________
From: portfolio-bounces@... [portfolio-bounces@...] On Behalf Of janice.smith [janice.smith@...]
Sent: Tuesday, November 24, 2009 5:15 PM
To: portfolio@...; pedagogy@...
Subject: [Portfolio] Portfolio capabilities added to Learning Capabilities spreadsheet

Dear OSP and T&L Communities

I have just finished a reorganization and rewriting of the Portfolio-related Vignettes from Sakai Confluence and have posted them on rows 74-98 on the Learning Capabilities Google Spreadsheet. The rewrite was necessary because the categories on our Confluence page are different from the categories on the Learning Capabilities spreadsheet. I attempted to fully preserve the intent of our original document.

The Learning Capabilities spreadsheet can be found at http://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en.

I invite comments and critiques from the OSP Community. (Please send them to me directly.) Let's make sure we tell our story well!

T&L friends - we are hopeful that you will see how many similarities there are between the needs of users in our two communities. We look forward to continued collaboration on the functionality of Sakai 3.0!

Janice

Janice A. Smith, Ph.D.
2009 Sakai Foundation Fellow
Three Canoes
1204 Laurel Avenue
Saint Paul, Minnesota 55104, USA
651-642-9069, 207-841-6262 (cell)
janice.smith@...<mailto:janice.smith@...>
jasmith@...<mailto:jasmith@...>
_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

[Portfolio] Portfolio capabilities added to Learning Capabilities spreadsheet

2009-11-24T14:15:55Z

Dear OSP and T&L Communities

I have just finished a reorganization and rewriting of the Portfolio-related Vignettes from Sakai Confluence and have posted them on rows 74-98 on the Learning Capabilities Google Spreadsheet. The rewrite was necessary because the categories on our Confluence page are different from the categories on the Learning Capabilities spreadsheet. I attempted to fully preserve the intent of our original document.

The Learning Capabilities spreadsheet can be found at http://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en.

I invite comments and critiques from the OSP Community. (Please send them to me directly.) Let's make sure we tell our story well!

T&L friends - we are hopeful that you will see how many similarities there are between the needs of users in our two communities. We look forward to continued collaboration on the functionality of Sakai 3.0!

Janice

Janice A. Smith, Ph.D.
2009 Sakai Foundation Fellow
Three Canoes
1204 Laurel Avenue
Saint Paul, Minnesota 55104, USA
651-642-9069, 207-841-6262 (cell)
janice.smith@...
jasmith@...

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] OSP Community contribution to the Learning Capabilities Google document

2009-11-24T13:31:18Z

Hi Janice,

It's great to see the OSP ideas being clearly articulated in the Learning Capabilities page. It's a great addition!

- David

From: janice.smith <janice.smith@...>
To: portfolio@...
Sent: Tue, November 24, 2009 1:22:53 PM
Subject: [Portfolio] OSP Community contribution to the Learning Capabilities Google document

Hi David

At our Monday meeting, I was asked by the OSP Community to translate our Confluence page on Portfolio-related Vignettes for addition to the Learning Capabilities page. Given that the categories across our two pages are very different, I am rewriting and reorganizing and will transfer the results all at one time today or tomorrow. We recognize that the many portfolio-like items you list below are already in the document and that some of what we suggest will be somewhat redundant, but choose to add our approximately twenty items rather than edit what is already there. Thank you for encouraging us to contribute!

Janice

Janice A. Smith, Ph.D.
2009 Sakai Foundation Fellow
Three Canoes
1204 Laurel Avenue
Saint Paul, Minnesota 55104, USA
651-642-9069, 207-841-6262 (cell)
janice.smith@...
jasmith@...

Subject: [Portfolio] Learning Capabilities spreadsheet
From: David Goodrum <davidgoodrum@...>
Date: Tue, 24 Nov 2009 07:40:37 -0800 (PST)
To: portfolio@...

------------------------- Contents -------------------------

There's been an increasing awareness of the brainstorming activity reflected in the Learning Capabilities spreadsheet:

http://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en

It's been interesting to see the level of collaboration the document has seen and how it has evolved because of that collaboration. According to Google docs, there's been at least 15 collaborators on the document... likely more, since no login is required to edit it -- it is a totally open brainstorming document right now.

The spreadsheet is certainly not exhaustive nor complete, nor is that the intent for this phase. It currently does not necessarily reflect the best capabilities of Sakai 2.x; it does not reflect what all is missing or frustrating about Sakai 2.x; it does not reflect all of what Sakai 3 should aspire to; it doesn't even fully represent what teaching and learning goals should be supported in Sakai 3. So what's the point?

With 60+ rows right now, it begins to represent a fair cross section of many ambitions Sakai 3 perhaps ought to have in the teaching and learning space.

And it attempts to show how different levels of complexity and functional capabilities both link together and link back to a basic teaching and learning goal, hopefully expressed in everyday language.

Perhaps a bad analogy for the document would be the recent cell coverage maps... Ideally, our teaching and learning map would look like Verizon's 3G map... with nearly the whole map filled in. This brainstorming document today is more like the AT&T 3G coverage map: a lot of white space still to be filled in, but there is coverage of many core areas and outlines of many others.

For now it's a place to play out some ideas.

Got a teaching and learning idea? Something instructors want their students to do? Something students wish instructors would do? Something that develops collaboration and cooperation among students, encourages active learning, gives prompt feedback, emphasizes time on task, communicates high expectations, or respects diverse talents and ways of learning? Then add it to the brainstorm.

And here are some ideas/language already in the document that seem related to Portfolio concepts (including an explicit reference/link in the last item to the important vignette development the OSP group has been refining):

Current row 9 "I need to track student learning"

I need to track student learning

Show details of expectations and levels of accomplishment Provide guidance, examples, rubrics. Link to portfolios of previous students of this course (with permission)

Publish and subscribe to goals; map heirarchical relationships between goals
Organize and track lifelong learning for the individual and the institution; track student progress over their entire academic career

Current row 19 "I want to give my students grades"

I want to provide feedback on submitted work; I want students to review and critique each other's work as well.

Feedback / comment with rich-text formatting and attachments for any object
Any object can receive a comment or grade; Grouping of objects (e.g., portfolio) that receive feedback; both open and structured feedback

Grades are a special case of feedback and non-numerical assessment should be supported; Instructor feedback; self feedback; peer feedback; external to class review; external to system review; multitude of permissions for who can see what

Current row 41 "I want to represent specific campus/school/program learning goals (and associated grading/assessment rubrics) as a framework for a large set of courses."

Goals and rubrics can be a way for an institution to differentiate itself through standards for excellence from other institutions and for showing that program X complies with Association Y's expectations.

Some goals and rubrics are rather specific must be approved by an "assessment coordinator" for educational QA purposes as part of a larger assessment system strategy. Changing the assessment/rubric in this case involves more than just an individual instructor.

Goals created by others (the individual student or instructor or a particular program) can be mapped to larger campus/school goals. Some rubrics may be general purpose rubrics that are NOT tied to an assessment, but the dissemination of these approved rubrics may be a strategy of an institution to push forward an agenda of best practice for assessment by providing a handy reference library of general purpose writing, mathematics and science rubrics (for example). While the choice whether or not to use one of these "off the shelf" rubrics (and which one) is left to the teacher, providing some information to the teacher about the schools expectations of its students at different stages (and perhaps suggesting an appropriate rubric for this grade level/stage of development) would make this service more valuable.

Some items in the library of "off the shelf" goals and rubrics are merely starting points. There is not a priority to ensure that everyone is doing assessment the exact same way. When a teacher uses one of these rubrics, they can easily edit the performance indicators to suit their needs and create a new rubric, just for their new assignment. Goals and rubrics can be shared with others. This is a bottom up approach to establishing "best practice". As the teachers create their own rubrics against goals, they have the opportunity to publish them as part of the "reusable" library so other teachers can use/edit/republish them.

[note that this was largely copied and paste from a posting Sean Keesler made to one of the lists]

Current line 43 "I want to encourage and at times require students to reflect on the task I have them doing.

I want to add a guided metacognitive aspect to tasks I give students.

This might be an open ended reflection. But this might be also a structured reflection, for example ask them to rate their confidence in a task (or even for an individual question I've asked them), or to classify their contribution to a task or discussion (e.g., claim, reason, evidence, warrant, or acknowledgement/response).

Current line 52 "I want to create an analytic rubric or holistic, share it with my students, and use it to grade and/or evaluate an open-ended assignment"

Tool for generating analytic and holstic rubrics. Instructor enters criteria, rating scale, and characterisics of work associated with each point on the scale. Rubric can be attached to any example of student work and isntructor can opt to display to students before submission. To grade or evaluate, instructor clicks or selects the rating for each criterion. Students see a read only version of the rubric with the instructions rating selections.

Instructors can easily classify and share rubrics with specific colleagues, their department, program, campus , and/or the public. Rubrics can be associated with learning outcomes/goals.

Current line 56 "I want my students to keep a log or journal on their experience in this course."

Current line 70 "I want to continue to have access to all of my work products after the class and even after I graduate."

Current line 72 "Support for wide range of portfolio related activities: Guide, Collect, Reflect, Tag, Associate, Evaluate, Share, Report, Flow, Assess, Present, Customize, Preserve, Document, Collaborate, Own, Empower, Re-purpose, Port, Express, Migrate"

See Portfolio vignettes:
http://confluence.sakaiproject.org/display/UX/Portfolio-related+vignettes

So please feel free to add to or expand something already there. Or at least take a look and see how this brainstorming exercise is evolving. This activity may help to identify functions that various Sakai groups are exploring.

Regards - David

[Portfolio] OSP Community contribution to the Learning Capabilities Google document

2009-11-24T10:22:53Z

Hi David

At our Monday meeting, I was asked by the OSP Community to translate our Confluence page on Portfolio-related Vignettes for addition to the Learning Capabilities page. Given that the categories across our two pages are very different, I am rewriting and reorganizing and will transfer the results all at one time today or tomorrow. We recognize that the many portfolio-like items you list below are already in the document and that some of what we suggest will be somewhat redundant, but choose to add our approximately twenty items rather than edit what is already there. Thank you for encouraging us to contribute!

Janice

Janice A. Smith, Ph.D.
2009 Sakai Foundation Fellow
Three Canoes
1204 Laurel Avenue
Saint Paul, Minnesota 55104, USA
651-642-9069, 207-841-6262 (cell)
janice.smith@...
jasmith@...

Subject: [Portfolio] Learning Capabilities spreadsheet
From: David Goodrum <davidgoodrum@...>
Date: Tue, 24 Nov 2009 07:40:37 -0800 (PST)
To: portfolio@...

------------------------- Contents -------------------------

There's been an increasing awareness of the brainstorming activity reflected in the Learning Capabilities spreadsheet:

http://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en

With 60+ rows right now, it begins to represent a fair cross section of many ambitions Sakai 3 perhaps ought to have in the teaching and learning space.

For now it's a place to play out some ideas.

Current row 9 "I need to track student learning"

I need to track student learning

Show details of expectations and levels of accomplishment Provide guidance, examples, rubrics. Link to portfolios of previous students of this course (with permission)

Publish and subscribe to goals; map heirarchical relationships between goals
Organize and track lifelong learning for the individual and the institution; track student progress over their entire academic career

Current row 19 "I want to give my students grades"

I want to provide feedback on submitted work; I want students to review and critique each other's work as well.

Feedback / comment with rich-text formatting and attachments for any object
Any object can receive a comment or grade; Grouping of objects (e.g., portfolio) that receive feedback; both open and structured feedback

Grades are a special case of feedback and non-numerical assessment should be supported; Instructor feedback; self feedback; peer feedback; external to class review; external to system review; multitude of permissions for who can see what

Current row 41 "I want to represent specific campus/school/program learning goals (and associated grading/assessment rubrics) as a framework for a large set of courses."

Goals and rubrics can be a way for an institution to differentiate itself through standards for excellence from other institutions and for showing that program X complies with Association Y's expectations.

Some goals and rubrics are rather specific must be approved by an "assessment coordinator" for educational QA purposes as part of a larger assessment system strategy. Changing the assessment/rubric in this case involves more than just an individual instructor.

Goals created by others (the individual student or instructor or a particular program) can be mapped to larger campus/school goals. Some rubrics may be general purpose rubrics that are NOT tied to an assessment, but the dissemination of these approved rubrics may be a strategy of an institution to push forward an agenda of best practice for assessment by providing a handy reference library of general purpose writing, mathematics and science rubrics (for example). While the choice whether or not to use one of these "off the shelf" rubrics (and which one) is left to the teacher, providing some information to the teacher about the schools expectations of its students at different stages (and perhaps suggesting an appropriate rubric for this grade level/stage of development) would make this service more valuable.

Some items in the library of "off the shelf" goals and rubrics are merely starting points. There is not a priority to ensure that everyone is doing assessment the exact same way. When a teacher uses one of these rubrics, they can easily edit the performance indicators to suit their needs and create a new rubric, just for their new assignment. Goals and rubrics can be shared with others. This is a bottom up approach to establishing "best practice". As the teachers create their own rubrics against goals, they have the opportunity to publish them as part of the "reusable" library so other teachers can use/edit/republish them.

[note that this was largely copied and paste from a posting Sean Keesler made to one of the lists]

Current line 43 "I want to encourage and at times require students to reflect on the task I have them doing.

I want to add a guided metacognitive aspect to tasks I give students.

This might be an open ended reflection. But this might be also a structured reflection, for example ask them to rate their confidence in a task (or even for an individual question I've asked them), or to classify their contribution to a task or discussion (e.g., claim, reason, evidence, warrant, or acknowledgement/response).

Current line 52 "I want to create an analytic rubric or holistic, share it with my students, and use it to grade and/or evaluate an open-ended assignment"

Tool for generating analytic and holstic rubrics. Instructor enters criteria, rating scale, and characterisics of work associated with each point on the scale. Rubric can be attached to any example of student work and isntructor can opt to display to students before submission. To grade or evaluate, instructor clicks or selects the rating for each criterion. Students see a read only version of the rubric with the instructions rating selections.

Instructors can easily classify and share rubrics with specific colleagues, their department, program, campus , and/or the public. Rubrics can be associated with learning outcomes/goals.

Current line 56 "I want my students to keep a log or journal on their experience in this course."

Current line 70 "I want to continue to have access to all of my work products after the class and even after I graduate."

See Portfolio vignettes:
http://confluence.sakaiproject.org/display/UX/Portfolio-related+vignettes

Regards - David

[Portfolio] Learning Capabilities spreadsheet

2009-11-24T07:40:37Z

There's been an increasing awareness of the brainstorming activity reflected in the Learning Capabilities spreadsheet:

http://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en

With 60+ rows right now, it begins to represent a fair cross section of many ambitions Sakai 3 perhaps ought to have in the teaching and learning space.

For now it's a place to play out some ideas.

Current row 9 "I need to track student learning"

I need to track student learning

Show details of expectations and levels of accomplishment Provide guidance, examples, rubrics. Link to portfolios of previous students of this course (with permission)

Publish and subscribe to goals; map heirarchical relationships between goals
Organize and track lifelong learning for the individual and the institution; track student progress over their entire academic career

Current row 19 "I want to give my students grades"

I want to provide feedback on submitted work; I want students to review and critique each other's work as well.

Feedback / comment with rich-text formatting and attachments for any object
Any object can receive a comment or grade; Grouping of objects (e.g., portfolio) that receive feedback; both open and structured feedback

Grades are a special case of feedback and non-numerical assessment should be supported; Instructor feedback; self feedback; peer feedback; external to class review; external to system review; multitude of permissions for who can see what

Current row 41 "I want to represent specific campus/school/program learning goals (and associated grading/assessment rubrics) as a framework for a large set of courses."

Goals and rubrics can be a way for an institution to differentiate itself through standards for excellence from other institutions and for showing that program X complies with Association Y's expectations.

Some goals and rubrics are rather specific must be approved by an "assessment coordinator" for educational QA purposes as part of a larger assessment system strategy. Changing the assessment/rubric in this case involves more than just an individual instructor.

Goals created by others (the individual student or instructor or a particular program) can be mapped to larger campus/school goals. Some rubrics may be general purpose rubrics that are NOT tied to an assessment, but the dissemination of these approved rubrics may be a strategy of an institution to push forward an agenda of best practice for assessment by providing a handy reference library of general purpose writing, mathematics and science rubrics (for example). While the choice whether or not to use one of these "off the shelf" rubrics (and which one) is left to the teacher, providing some information to the teacher about the schools expectations of its students at different stages (and perhaps suggesting an appropriate rubric for this grade level/stage of development) would make this service more valuable.

Some items in the library of "off the shelf" goals and rubrics are merely starting points. There is not a priority to ensure that everyone is doing assessment the exact same way. When a teacher uses one of these rubrics, they can easily edit the performance indicators to suit their needs and create a new rubric, just for their new assignment. Goals and rubrics can be shared with others. This is a bottom up approach to establishing "best practice". As the teachers create their own rubrics against goals, they have the opportunity to publish them as part of the "reusable" library so other teachers can use/edit/republish them.

[note that this was largely copied and paste from a posting Sean Keesler made to one of the lists]

Current line 43 "I want to encourage and at times require students to reflect on the task I have them doing.

I want to add a guided metacognitive aspect to tasks I give students.

This might be an open ended reflection. But this might be also a structured reflection, for example ask them to rate their confidence in a task (or even for an individual question I've asked them), or to classify their contribution to a task or discussion (e.g., claim, reason, evidence, warrant, or acknowledgement/response).

Current line 52 "I want to create an analytic rubric or holistic, share it with my students, and use it to grade and/or evaluate an open-ended assignment"

Tool for generating analytic and holstic rubrics. Instructor enters criteria, rating scale, and characterisics of work associated with each point on the scale. Rubric can be attached to any example of student work and isntructor can opt to display to students before submission. To grade or evaluate, instructor clicks or selects the rating for each criterion. Students see a read only version of the rubric with the instructions rating selections.

Instructors can easily classify and share rubrics with specific colleagues, their department, program, campus , and/or the public. Rubrics can be associated with learning outcomes/goals.

Current line 56 "I want my students to keep a log or journal on their experience in this course."

Current line 70 "I want to continue to have access to all of my work products after the class and even after I graduate."

See Portfolio vignettes:
http://confluence.sakaiproject.org/display/UX/Portfolio-related+vignettes

Regards - David

From: Clay Fenlason <clay.fenlason@...>
To: Sakai UX <sakai-ux@...>; pedagogy Learning <pedagogy@...>
Sent: Wed, November 18, 2009 7:28:43 PM
Subject: [DG: User Experience] Leading Design

In recent weeks I've been trying to promote the maturation of the
learning capabilities spreadsheet [1] that David Goodrum has
championed. At the same time I've heard concerns that it might come to
naught or not be listened to. Just a couple days ago Josh Baron was
asking me when and how I thought the spreadsheet might actually be
used to inform the design. I told him, "It's happening right now." I'm
not sure he believed me, so I made a blog post with evidence:
http://sakaipm.wordpress.com

~Clay

[1] https://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en
_______________________________________________
sakai-ux mailing list
sakai-ux@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-ux

TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"

_______________________________________________
pedagogy mailing list
pedagogy@...
http://collab.sakaiproject.org/mailman/listinfo/pedagogy

TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe"
_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] portfolio Digest, Vol 9, Issue 24

2009-11-24T07:40:36Z

Thank you for contacting me. I am out of the office until November 30th and will get back to you then. Have a wonderful holiday!

Re: [Portfolio] Portfolio goals and the Google Spreadsheet

2009-11-24T07:29:06Z

Thanks, Clay.

I'm forwarding this along to the portfolio group.
I'm not sure we are ready for that level of specificity yet, but it's good to see what "design" is shaping up to look like.

Sean

On Tue, Nov 24, 2009 at 9:08 AM, Clay Fenlason <clay.fenlason@...> wrote:

Hi Sean:

Thanks for the note. I've heard by other channels that there is
concern about this apparent duplication of effort, and I at least
wanted to make the point that the spreadsheet format isn't required in
order to be listened to. It's also the case that the spreadsheet seems
to be a good exercise for functional experts, but the shape we'll be
driving toward to really inform design will be more something like the
user charts in the middle of this PDF:

http://sakaipm.files.wordpress.com/2009/11/assignmentslessons.pdf

If aiming for that kind of user-based chart seems a better way to
build on the OSP thinking that has already happened, and may perhaps
be a bit easier to swallow without feeling like it's doing the same
thing over again, I might suggest that as an alternative format.

~Clay

On Mon, Nov 23, 2009 at 12:08 PM, Sean Keesler
<sean.keesler@...> wrote:
> Hi, Clay.
>
> I'm sure you know that the portfolio group has a bunch of ideas on a
> separate confluence page:
> http://confluence.sakaiproject.org/display/UX/Portfolio-related+vignettes
>
> We think we probably should do a bit of work to translate that confluence
> page into the google doc you and so many are looking at.
> It isn't that we think that the confluence page is unknown, but there is an
> artificial barrier that still exists between these groups that we would like
> to bridge by "translating" our "verbs" into the "goals" of the spreadsheet,
> as we feel that the needs are probably universal.
>
> On last weeks T&L call, some reference was made to an upcoming date of Dec 2
> as some significance to that spreadsheet.
> We want to get our info into that spreadsheet before then.
>
> Sean Keesler
> 130 Academy Street
> Manlius, New York 13104 USA
> 315-663-7756
> sean.keesler@...
>

Re: [Portfolio] portfolio Digest, Vol 9, Issue 23

2009-11-23T11:59:53Z

Thank you for contacting me. I am out of the office until November 30th and will get back to you then. Have a wonderful holiday!

Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

2009-11-22T14:02:37Z

Thanks, Sean. This is a helpful sample for isolating the issue. Your account tells me that SAK-17423 is well placed and that we have some work to do.

Thanks,

-Noah

On Nov 21, 2009, at 10:12 AM, Sean Keesler wrote:

This works different for a form renderer than in a portfolio template.

I have a simple xsl file (using the relative path that seems to work for everyone):

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
    <xsl:import href="/group/PortfolioAdmin/authoring/passthrough.xsl"/>

    <xsl:template match="/">
        <xsl:text>Hey there!</xsl:text>
    </xsl:template>

</xsl:stylesheet>

When I use that xsl file for a form renderer, I get "Hey there"...just as I expect.
When I use it in a portfolio template, I get an error in the logs:

ERROR: '/group/PortfolioAdmin/authoring/passthrough.xsl (No such file or directory)'
FATAL ERROR: 'Could not compile stylesheet'

Isn't that weird?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

2009-11-21T07:12:11Z

This works different for a form renderer than in a portfolio template.

I have a simple xsl file (using the relative path that seems to work for everyone):

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
    <xsl:import href="/group/PortfolioAdmin/authoring/passthrough.xsl"/>

    <xsl:template match="/">
        <xsl:text>Hey there!</xsl:text>
    </xsl:template>

</xsl:stylesheet>

When I use that xsl file for a form renderer, I get "Hey there"...just as I expect.
When I use it in a portfolio template, I get an error in the logs:

ERROR: '/group/PortfolioAdmin/authoring/passthrough.xsl (No such file or directory)'
FATAL ERROR: 'Could not compile stylesheet'

Isn't that weird?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Fri, Nov 20, 2009 at 6:58 PM, Noah Botimer <botimer@...> wrote:

In general, the Content Hosting URI resolver should be in place when these XSLs execute. That means that an import on something like '/group/PortfolioAdmin/...xsl' should be valid. This also insulates your XSL from instance/hostname changes and so on. You will want to make sure that anything included/imported is public in Resources.

The tricky bit here is that XSL includes and so on that are not fully qualified URLs are not evaluated the same as they would by a browser. They are resolved locally, which, if the CHS glue isn't in place, will be somewhere deep in the app server (essentially useless). If we find that this is the case anywhere, we should fix it.

Note that this means '/access/content/group/PortfolioAdmin' is incorrect for things like include/import. It is, however, correct for referencing accessible items that the browser would hit (script, images, or stylesheets). There is a different construction for "additional materials" attached to a template, where you would typically pass the path from the XML to sakaifn:getReferenceUrl. (You can also pass your items like script URLs to getReferenceUrl if you remove /access/content.)

I cannot speak to the http/https behavior or the DTD 503s aside from that we should make sure that the local catalog is registered everywhere as in http://jira.sakaiproject.org/browse/SAK-16536. Along with local, internal references to your supplemental materials, this should make sure that your server isn't attempting external requests for what it needs.

Thanks,
-Noah

On Nov 20, 2009, at 4:16 PM, hongbo zhang wrote:

I just tested it with the localhost 2.6.0 instance.

If I write

<xsl:include href="http://localhost:8080/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl"/>

It does not work. It complains the stylesheet can not be complied.

However if I use

<xsl:include href="https://scholar.vt.edu/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl"/>


It works.

I attached the worked screen shot as well as the template file for the 2.6.0 test. The texts on the front page comes from a template in another xsl file.

However, interestingly, both localhost and permanent URL methods work for 2.5.3 instance.

I guess, the permanent URL is important for 2.6. The URL should not be in the localhost. It should be a good workable URL. Many times, we use localhost for development, which might give some trouble.

Just a thought.

Hongbo

From: sean@... [sean@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 12:35 PM
To: Maurer, Christopher Wayne
Cc: Ackerman, Erica; hongbo zhang; osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

I'm pretty sure it's importing the 2nd file...if I change the url, I get an error that it can't find the file to import...
My 2nd file is dirt simple...a passthrough stylesheet...just to test.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Fri, Nov 20, 2009 at 11:56 AM, Maurer, Christopher Wayne <chmaurer@...> wrote:

The only difference I see is that Sean's import uses a full url to the xsl file while Erica's is just a path to a content resource.

Not sure if that makes a difference or not, but worth noting!

Chris

On Nov 20, 2009, at 11:34 AM, Ackerman, Erica wrote:

Sean,

We use xsl:import in the Page Composer, and it works in 2.6 and 2.5 both.

For example:

<xsl:stylesheet version="1.0" xmlns="http://www.w3.org/1999/xhtml" xmlns:sakaifn="org.sakaiproject.metaobj.utils.xml.XsltFunctions" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:osp="http://www.osportfolio.org/OspML" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xsl:output method="html" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
    <xsl:import href="/group/PortfolioAdmin/authoring/xsl/formCreate-wysiwyg.xsl" />

Could there be something wrong with the imported file?

Erica

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 10:33 AM
To: hongbo zhang
Cc: osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

I wonder if this is a 2.6-only issue.
Have you tried your template in a 2.6 instance?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Thu, Nov 19, 2009 at 3:41 PM, hongbo zhang <hbzhang@...> wrote:

I just tried using xsl:include. It works great.

I attached the sample file.

This is the template xsl file used in single form template. I include another xsl file, which has several templates. I just try to call it           <xsl:call-template name="Tab1instruction"></xsl:call-template> at line 743.

It seems it works fine for me. We run 2.5.4 instance.

Hongbo

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Thursday, November 19, 2009 3:10 PM
To: osp
Subject: [Portfolio] 503 for DTD request in templated portfolios that import other templates

Has anyone developed a portfolio template using an xsl file that imports other xsl files?
Like this:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">


<xsl:import href="http://yourserver.edu/path/to/your/imported.xsl"/>

   <xsl:template match="/">
     <xsl:text>Hey there!</xsl:text>
   </xsl:template>

</xsl:stylesheet>

When I do, I get a 503 error in the logs related to DTD issues.

I wrote it up as http://jira.sakaiproject.org/browse/SAK-17423.
It seems like it is similar to the stack trace that was occurring in free form portfolios in http://jira.sakaiproject.org/browse/SAK-16536.

This is 2-6-x branch r69087.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

<test.JPG><portfoliotemplate.xsl>
_______________________________________________
portfolio mailing list
portfolio@...

http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

2009-11-20T15:58:36Z

In general, the Content Hosting URI resolver should be in place when these XSLs execute. That means that an import on something like '/group/PortfolioAdmin/...xsl' should be valid. This also insulates your XSL from instance/hostname changes and so on. You will want to make sure that anything included/imported is public in Resources.

The tricky bit here is that XSL includes and so on that are not fully qualified URLs are not evaluated the same as they would by a browser. They are resolved locally, which, if the CHS glue isn't in place, will be somewhere deep in the app server (essentially useless). If we find that this is the case anywhere, we should fix it.

Note that this means '/access/content/group/PortfolioAdmin' is incorrect for things like include/import. It is, however, correct for referencing accessible items that the browser would hit (script, images, or stylesheets). There is a different construction for "additional materials" attached to a template, where you would typically pass the path from the XML to sakaifn:getReferenceUrl. (You can also pass your items like script URLs to getReferenceUrl if you remove /access/content.)

I cannot speak to the http/https behavior or the DTD 503s aside from that we should make sure that the local catalog is registered everywhere as in http://jira.sakaiproject.org/browse/SAK-16536. Along with local, internal references to your supplemental materials, this should make sure that your server isn't attempting external requests for what it needs.

Thanks,

-Noah

On Nov 20, 2009, at 4:16 PM, hongbo zhang wrote:

I just tested it with the localhost 2.6.0 instance.

If I write

<xsl:include href="http://localhost:8080/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl"/>

It does not work. It complains the stylesheet can not be complied.

However if I use

<xsl:include href="https://scholar.vt.edu/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl"/>

It works.

I attached the worked screen shot as well as the template file for the 2.6.0 test. The texts on the front page comes from a template in another xsl file.

However, interestingly, both localhost and permanent URL methods work for 2.5.3 instance.

I guess, the permanent URL is important for 2.6. The URL should not be in the localhost. It should be a good workable URL. Many times, we use localhost for development, which might give some trouble.

Just a thought.

Hongbo

From: sean@... [sean@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 12:35 PM
To: Maurer, Christopher Wayne
Cc: Ackerman, Erica; hongbo zhang; osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

I'm pretty sure it's importing the 2nd file...if I change the url, I get an error that it can't find the file to import...
My 2nd file is dirt simple...a passthrough stylesheet...just to test.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Fri, Nov 20, 2009 at 11:56 AM, Maurer, Christopher Wayne <chmaurer@...> wrote:

The only difference I see is that Sean's import uses a full url to the xsl file while Erica's is just a path to a content resource.

Not sure if that makes a difference or not, but worth noting!

Chris

On Nov 20, 2009, at 11:34 AM, Ackerman, Erica wrote:

Sean,

We use xsl:import in the Page Composer, and it works in 2.6 and 2.5 both.

For example:

<xsl:stylesheet version="1.0" xmlns="http://www.w3.org/1999/xhtml" xmlns:sakaifn="org.sakaiproject.metaobj.utils.xml.XsltFunctions" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:osp="http://www.osportfolio.org/OspML" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xsl:output method="html" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
    <xsl:import href="/group/PortfolioAdmin/authoring/xsl/formCreate-wysiwyg.xsl" />

Could there be something wrong with the imported file?

Erica

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 10:33 AM
To: hongbo zhang
Cc: osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

I wonder if this is a 2.6-only issue.
Have you tried your template in a 2.6 instance?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Thu, Nov 19, 2009 at 3:41 PM, hongbo zhang <hbzhang@...> wrote:

I just tried using xsl:include. It works great.

I attached the sample file.

This is the template xsl file used in single form template. I include another xsl file, which has several templates. I just try to call it           <xsl:call-template name="Tab1instruction"></xsl:call-template> at line 743.

It seems it works fine for me. We run 2.5.4 instance.

Hongbo

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Thursday, November 19, 2009 3:10 PM
To: osp
Subject: [Portfolio] 503 for DTD request in templated portfolios that import other templates

Has anyone developed a portfolio template using an xsl file that imports other xsl files?
Like this:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">


<xsl:import href="http://yourserver.edu/path/to/your/imported.xsl"/>

   <xsl:template match="/">
     <xsl:text>Hey there!</xsl:text>
   </xsl:template>

</xsl:stylesheet>

When I do, I get a 503 error in the logs related to DTD issues.

I wrote it up as http://jira.sakaiproject.org/browse/SAK-17423.
It seems like it is similar to the stack trace that was occurring in free form portfolios in http://jira.sakaiproject.org/browse/SAK-16536.

This is 2-6-x branch r69087.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

<test.JPG><portfoliotemplate.xsl>
_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

2009-11-20T13:16:24Z

I just tested it with the localhost 2.6.0 instance.

If I write

<xsl:include href="http://localhost:8080/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl"/>

It does not work. It complains the stylesheet can not be complied.

However if I use

<xsl:include href="https://scholar.vt.edu/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl"/>

It works.

I attached the worked screen shot as well as the template file for the 2.6.0 test. The texts on the front page comes from a template in another xsl file.

However, interestingly, both localhost and permanent URL methods work for 2.5.3 instance.

I guess, the permanent URL is important for 2.6. The URL should not be in the localhost. It should be a good workable URL. Many times, we use localhost for development, which might give some trouble.

Just a thought.

Hongbo

From: sean@... [mailto:sean@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 12:35 PM
To: Maurer, Christopher Wayne
Cc: Ackerman, Erica; hongbo zhang; osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

I'm pretty sure it's importing the 2nd file...if I change the url, I get an error that it can't find the file to import...
My 2nd file is dirt simple...a passthrough stylesheet...just to test.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Fri, Nov 20, 2009 at 11:56 AM, Maurer, Christopher Wayne <chmaurer@...> wrote:

The only difference I see is that Sean's import uses a full url to the xsl file while Erica's is just a path to a content resource.

Not sure if that makes a difference or not, but worth noting!

Chris

On Nov 20, 2009, at 11:34 AM, Ackerman, Erica wrote:

Sean,

We use xsl:import in the Page Composer, and it works in 2.6 and 2.5 both.

For example:

<xsl:stylesheet version="1.0" xmlns="http://www.w3.org/1999/xhtml" xmlns:sakaifn="org.sakaiproject.metaobj.utils.xml.XsltFunctions" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:osp="http://www.osportfolio.org/OspML" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xsl:output method="html" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
    <xsl:import href="/group/PortfolioAdmin/authoring/xsl/formCreate-wysiwyg.xsl" />

Could there be something wrong with the imported file?

Erica

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 10:33 AM
To: hongbo zhang
Cc: osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

I wonder if this is a 2.6-only issue.
Have you tried your template in a 2.6 instance?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Thu, Nov 19, 2009 at 3:41 PM, hongbo zhang <hbzhang@...> wrote:

I just tried using xsl:include. It works great.

I attached the sample file.

This is the template xsl file used in single form template. I include another xsl file, which has several templates. I just try to call it           <xsl:call-template name="Tab1instruction"></xsl:call-template> at line 743.

It seems it works fine for me. We run 2.5.4 instance.

Hongbo

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Thursday, November 19, 2009 3:10 PM
To: osp
Subject: [Portfolio] 503 for DTD request in templated portfolios that import other templates

Has anyone developed a portfolio template using an xsl file that imports other xsl files?
Like this:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">


<xsl:import href="http://yourserver.edu/path/to/your/imported.xsl"/>

   <xsl:template match="/">
     <xsl:text>Hey there!</xsl:text>
   </xsl:template>

</xsl:stylesheet>

When I do, I get a 503 error in the logs related to DTD issues.

I wrote it up as http://jira.sakaiproject.org/browse/SAK-17423.
It seems like it is similar to the stack trace that was occurring in free form portfolios in http://jira.sakaiproject.org/browse/SAK-16536.

This is 2-6-x branch r69087.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

<!DOCTYPE xsl:stylesheet [
<!ENTITY lower 'abcdefghijklmnopqrstuvwxyz'>
<!ENTITY upper 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'>
]>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns:sakaifn="org.sakaiproject.metaobj.utils.xml.XsltFunctions" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xalan="http://xml.apache.org/xalan">
<xsl:output method="html" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>






<xsl:include href="https://scholar.vt.edu/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl"/>

<xsl:attribute-set name="objectproperty">
<xsl:attribute name="classid">clsid:D27CDB6E-AE6D-11cf-96B8-444553540000</xsl:attribute>
<xsl:attribute name="codebase">http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=5,0,0,0</xsl:attribute>
<xsl:attribute name="width">553</xsl:attribute>
<xsl:attribute name="height">700</xsl:attribute>
</xsl:attribute-set>

<xsl:param name="id"/>
<xsl:param name="mode" select="'view'"/>
<xsl:param name="page"/>
<xsl:param name="sakai.tool.placement.id"/>




<xsl:variable name="authoringPath"><xsl:value-of select="sakaifn:getReferenceUrl('/group/PortfolioAdmin/authoring/')"/></xsl:variable>

<xsl:variable name="themeRepo" select="concat($authoringPath, 'themeEPATVT/')"/>
<xsl:variable name="sitename">Epatvt</xsl:variable>

<xsl:template match="ospiPresentation">
<xsl:variable name="ieComments">  </xsl:variable>
<xsl:variable name="pageOrder">BackgroundFrontPage ParticipantsFrontPage ProgramsfrontPage ResourcefrontPage ReflectionFrontPage FundingFrontPage PicturesPage OtherFrontPage ContactPage</xsl:variable>


<xsl:variable name="multiOrder"> { "slots": [<xsl:for-each select="*[contains(name(), 'Page')]"><xsl:sort select="string-length(substring-after($pageOrder, name()))" order="descending"/><xsl:sort select="name()"/> { "<xsl:value-of select="name()"/>": [<xsl:for-each select="artifact[1]/schema//element[@name = 'secondaryCategory']//xs:enumeration/@value"><xsl:variable name="thisCat" select="."/> { "<xsl:value-of select="."/>":
[<xsl:for-each select="ancestor::artifact/../artifact[structuredData/*/secondaryCategory = $thisCat]"><xsl:sort select="structuredData/*/sortOrder"/><xsl:sort select="structuredData/*/title"/> { "<xsl:value-of select="metaData/id"/>": "<xsl:value-of select="structuredData/*/title"/>" }<xsl:if test="position() != last()">, </xsl:if></xsl:for-each> ]<xsl:if test="position() != last()"> }, </xsl:if></xsl:for-each> ] }<xsl:if test="position() != last()">,
</xsl:if></xsl:for-each> ] }</xsl:variable>
<xsl:variable name="theme">
<xsl:value-of select="presentationProperties/portfolioOptiions/theme"/>
</xsl:variable>
<xsl:variable name="portfolio.title">
<xsl:value-of select="presentationProperties/portfolioOptiions/portfolioTitle"/>
</xsl:variable>
<xsl:variable name="portfolio.owner">
<xsl:value-of select="presentationProperties/portfolioOptiions/username"/>
</xsl:variable>

<xsl:variable name="portfolio.organization">VT ePortfolio</xsl:variable>
<html>
<head>
<title>
<xsl:value-of select="$portfolio.title"/>
</title>
<link type="text/css" rel="stylesheet" media="all" href="{$authoringPath}css/impromptu.css"/>
<link type="text/css" rel="stylesheet" media="all" href="{$themeRepo}css/comment.css"/>
<link type="text/css" rel="stylesheet" media="all" href="{$themeRepo}{$theme}/{$theme}.css" title="{$theme}"/>
<link type="text/css" rel="stylesheet" media="all" href="{$authoringPath}css/basic.css"/>
<link type="text/css" rel="stylesheet" media="all" href="{$authoringPath}css/buttons.css"/>
<link type="text/css" rel="stylesheet" media="all" href="{$themeRepo}{$theme}/secondarymenudisplay.css"/>
<link type="text/css" rel="stylesheet" media="all" href="{$authoringPath}css/slideshow.css"/>

<script type="text/javascript" language="JavaScript" >
<xsl:variable name = "bannerimage" select="BannerImagepage/artifact/fileArtifact"/>
<xsl:variable name = "isheaderimage" select="HeaderImagepage/artifact/fileArtifact"/>
var banner, customizedheader;
banner = '<xsl:value-of select="$bannerimage"/>';
customizedheader = '<xsl:value-of select="$isheaderimage"/>';
</script>

<xsl:value-of select="$ieComments" disable-output-escaping="yes"/>
<script type="text/javascript" src="{$authoringPath}js/jquery-1.2.1.min.js"> //empty </script>
<script type="text/javascript" src="{$authoringPath}lib/jquery.cookie.js">//empty </script>
<script type="text/javascript" src="{$authoringPath}lib/jquery.timer.js"> //empty </script>
<script type="text/javascript" src="{$authoringPath}js/swfobject.js">//empty</script>
<script type="text/javascript" src="{$authoringPath}js/AC_QuickTime.js"> //empty </script>
<script type="text/javascript">var portfolioId = "<xsl:value-of select="$id"/>";</script>
<script type="text/javascript" src="{$authoringPath}lib/json2.js">//empty</script>
<script type="text/javascript">var portfolioMode = 'view';</script>
<script type="text/javascript" src="{$themeRepo}{$theme}/portfolioQEP.js">//empty</script>
<script type="text/javascript" src="{$authoringPath}js/jquery.innerfade.js"> //empty </script>


</head>
<body>



<xsl:variable name="isTab1Front">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab11'">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="Tab1CustomizedTitle">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab11' ">
<xsl:value-of select="Title11"/>
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab1Other">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab12' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab2Front">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab21' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="Tab2CustomizedTitle">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab21' ">
<xsl:value-of select="Title21"/>
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab2Other">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab22' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab3Front">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab31' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="Tab3CustomizedTitle">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab31' ">
<xsl:value-of select="Title31"/>
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab3Other">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab32' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab4Front">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab41' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="Tab4CustomizedTitle">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab41' ">
<xsl:value-of select="Title41"/>
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab4Other">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab42' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab5Front">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab51' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="Tab5CustomizedTitle">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab51' ">
<xsl:value-of select="Title51"/>
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab5Other">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab52' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab6Front">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab61' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="Tab6CustomizedTitle">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab61' ">
<xsl:value-of select="Title61"/>
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab6Other">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab62' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab7Front">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab71' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="Tab7CustomizedTitle">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab71' ">
<xsl:value-of select="Title71"/>
</xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:variable name="isTab7Other">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab72' ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>

<div id="vt_center_band_wrapper"/>

<div id="portfolio_wrapper">

<div id="bgBodybkground">

<xsl:variable name = "isheaderimage" select="HeaderImagepage/artifact/fileArtifact"/>
<xsl:choose>
<xsl:when test="$isheaderimage">
<div id="portfolio_splash_customized">

<div id="portfolio_logo_customized">
<xsl:element name = "img">
<xsl:attribute name = "id">logoimg</xsl:attribute>
<xsl:attribute name = "alt">Title image</xsl:attribute>
<xsl:attribute name = "name">mmdimg</xsl:attribute>
<xsl:variable name = "headerimage" select="HeaderImagepage/artifact/fileArtifact"/>
<xsl:attribute name = "src"><xsl:value-of select="$headerimage"/></xsl:attribute>
<xsl:attribute name ="style">height:110px;</xsl:attribute>
</xsl:element>
</div>

<p id="portfolio_participant_name">
<xsl:value-of select="$portfolio.owner"/>
</p>
<p id="portfolio_title">
<xsl:value-of select="$portfolio.title"/>
</p>
</div>

</xsl:when>
<xsl:otherwise>
<div id="portfolio_splash">
<p id="portfolio_participant_name">
<xsl:value-of select="$portfolio.owner"/>
</p>
<p id="portfolio_title">
<xsl:value-of select="$portfolio.title"/>
</p>
</div>
</xsl:otherwise>
</xsl:choose>


<div id="portfolio_primary_navigation">
<ul id="primary_nav_list">


<xsl:if test="string-length($isTab1Front)>1 ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab111</xsl:attribute>
<xsl:choose>
<xsl:when test="string-length($Tab1CustomizedTitle)>1">
<xsl:value-of select="$Tab1CustomizedTitle"/>
</xsl:when>
<xsl:otherwise>
Home
</xsl:otherwise>
</xsl:choose>
</a>
</li>
</xsl:if>


<xsl:if test="string-length($isTab2Front)>1 ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab211</xsl:attribute>
<xsl:choose>
<xsl:when test="string-length($Tab2CustomizedTitle)>1">
<xsl:value-of select="$Tab2CustomizedTitle"/>
</xsl:when>
<xsl:otherwise>
Goal Statement
</xsl:otherwise>
</xsl:choose>
</a>
</li>
</xsl:if>


<xsl:if test="string-length($isTab3Front)>1 ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab311</xsl:attribute>
<xsl:choose>
<xsl:when test="string-length($Tab3CustomizedTitle)>1">
<xsl:value-of select="$Tab3CustomizedTitle"/>
</xsl:when>
<xsl:otherwise>
Philosophy
</xsl:otherwise>
</xsl:choose>
</a>
</li>
</xsl:if>


<xsl:if test="string-length($isTab4Front)>1 ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab411</xsl:attribute>
<xsl:choose>
<xsl:when test="string-length($Tab4CustomizedTitle)>1">
<xsl:value-of select="$Tab4CustomizedTitle"/>
</xsl:when>
<xsl:otherwise>
Work Showcase
</xsl:otherwise>
</xsl:choose>
</a>
</li>
</xsl:if>


<xsl:if test="string-length($isTab5Front)>1 ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab511</xsl:attribute>
<xsl:choose>
<xsl:when test="string-length($Tab5CustomizedTitle)>1">
<xsl:value-of select="$Tab5CustomizedTitle"/>
</xsl:when>
<xsl:otherwise>
Resume/CV
</xsl:otherwise>
</xsl:choose>
</a>
</li>
</xsl:if>


<xsl:if test="string-length($isTab6Front)>1 ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab611</xsl:attribute>
<xsl:choose>
<xsl:when test="string-length($Tab6CustomizedTitle)>1">
<xsl:value-of select="$Tab6CustomizedTitle"/>
</xsl:when>
<xsl:otherwise>
Other
</xsl:otherwise>
</xsl:choose>
</a>
</li>
</xsl:if>


<xsl:if test="string-length($isTab7Front)>1 ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab711</xsl:attribute>
<xsl:choose>
<xsl:when test="string-length($Tab7CustomizedTitle)>1">
<xsl:value-of select="$Tab7CustomizedTitle"/>
</xsl:when>
<xsl:otherwise>
Other...
</xsl:otherwise>
</xsl:choose>
</a>
</li>
</xsl:if>

</ul>
</div>

<xsl:variable name="videoshow" >
<xsl:for-each select="*[contains(name(), 'HomePage')]">
<xsl:for-each select="/ospiPresentation/Matrix/artifact/cells/cell">
<xsl:variable name="isVideoPage" select="scaffoldingCell/title"/>
<xsl:if test="contains($isVideoPage,'Home')">
<xsl:for-each select="wizardPage/attachments/attachment">
<xsl:variable name="position" select="position()"/>
<xsl:variable name="URLVideo" select="artifact/fileArtifact/uri"/>
<xsl:if test="contains($URLVideo, '.flv') or contains($URLVideo, '.swf')">
<br/>
<br/>

<div>
<xsl:attribute name="id">container<xsl:value-of select="$position"/></xsl:attribute>
<xsl:attribute name="align">center</xsl:attribute>
Play video here
</div>


<xsl:variable name="swfpath" select="concat($authoringPath, 'js/player-viral.swf')"/>
<xsl:element name="script">
<xsl:attribute name="LANGUAGE">javascript</xsl:attribute>
var s1 = new SWFObject("<xsl:value-of select="$swfpath"/>","player","215","200","9","#FFFFFF");
s1.addParam("allowfullscreen","true");
s1.addParam("allownetworking","all");
s1.addParam("allowscriptaccess","always");
s1.addParam("flashvars","file=<xsl:value-of select="$URLVideo"/>");
s1.write("container<xsl:value-of select="$position"/>");
</xsl:element>
</xsl:if>
</xsl:for-each>
</xsl:if>
</xsl:for-each>
</xsl:for-each>
</xsl:variable>


<div id="portfolio_page_body">

<div id="bgBody">
<div id="portfolio_secondary_navigation_1">
<div class="Nav" >
<abbr title="Virginia Tech E-Portfolio"><xsl:value-of select="$Tab1CustomizedTitle"/></abbr>
</div>

<ul id="secondary_nav_list_1">
<li>
<xsl:if test="string-length($isTab1Other)>1 ">

<ul class="subnav_list">

<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title12" order="ascending"/>
<xsl:sort select="Title12" order="ascending"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:variable name="position" select="position()"/>
<xsl:if test="$titlelink='ComplexTab12' ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab12<xsl:value-of select="$position"/></xsl:attribute>
<xsl:value-of select="Title12"/>
</a>
</li>
</xsl:if>
</xsl:for-each>
</ul>
</xsl:if>
</li>
</ul>
</div>

<div id="portfolio_secondary_navigation_2">
<div class="Nav" >
<abbr title="Virginia Tech E-Portfolio"><xsl:value-of select="$Tab2CustomizedTitle"/></abbr>
</div>

<ul id="secondary_nav_list_2">
<li>
<xsl:if test="string-length($isTab2Other)>1 ">

<ul class="subnav_list">

<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title22" order="ascending"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:variable name="position" select="position()"/>
<xsl:if test="$titlelink='ComplexTab22' ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab22<xsl:value-of select="$position"/></xsl:attribute>
<xsl:value-of select="Title22"/>
</a>
</li>
</xsl:if>
</xsl:for-each>
</ul>
</xsl:if>
</li>
</ul>
</div>

<div id="portfolio_secondary_navigation_3">
<div class="Nav" >
<abbr title="Virginia Tech E-Portfolio"><xsl:value-of select="$Tab3CustomizedTitle"/></abbr>
</div>

<ul id="secondary_nav_list_3">
<li>
<xsl:if test="string-length($isTab3Other)>1 ">

<ul class="subnav_list">

<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title32" order="ascending"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:variable name="position" select="position()"/>
<xsl:if test="$titlelink='ComplexTab32' ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab32<xsl:value-of select="$position"/></xsl:attribute>
<xsl:value-of select="Title32"/>
</a>
</li>
</xsl:if>
</xsl:for-each>
</ul>
</xsl:if>
</li>
</ul>
</div>

<div id="portfolio_secondary_navigation_4">
<div class="Nav" >
<abbr title="Virginia Tech E-Portfolio"><xsl:value-of select="$Tab4CustomizedTitle"/></abbr>
</div>

<ul id="secondary_nav_list_4">
<xsl:if test="string-length($isTab4Other)>1 ">
<xsl:call-template name="locateworkshowcase"/>
</xsl:if>
</ul>
</div>

<div id="portfolio_secondary_navigation_5">
<div class="Nav" >
<abbr title="Virginia Tech E-Portfolio"><xsl:value-of select="$Tab5CustomizedTitle"/></abbr>
</div>

<ul id="secondary_nav_list_5">
<li>
<xsl:if test="string-length($isTab5Other)>1 ">

<ul class="subnav_list">

<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title52" order="ascending"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:variable name="position" select="position()"/>
<xsl:if test="$titlelink='ComplexTab52' ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab52<xsl:value-of select="$position"/></xsl:attribute>
<xsl:value-of select="Title52"/>
</a>
</li>
</xsl:if>
</xsl:for-each>
</ul>
</xsl:if>
</li>
</ul>
</div>

<div id="portfolio_secondary_navigation_6">
<div class="Nav" >
<abbr title="Virginia Tech E-Portfolio"><xsl:value-of select="$Tab6CustomizedTitle"/></abbr>
</div>

<ul id="secondary_nav_list_6">
<li>
<xsl:if test="string-length($isTab6Other)>1 ">

<ul class="subnav_list">

<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title62" order="ascending"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:variable name="position" select="position()"/>
<xsl:if test="$titlelink='ComplexTab62' ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab62<xsl:value-of select="$position"/></xsl:attribute>
<xsl:value-of select="Title62"/>
</a>
</li>
</xsl:if>
</xsl:for-each>
</ul>
</xsl:if>
</li>
</ul>
</div>

<div id="portfolio_secondary_navigation_7">
<div class="Nav" >
<abbr title="Virginia Tech E-Portfolio"><xsl:value-of select="$Tab7CustomizedTitle"/></abbr>
</div>

<ul id="secondary_nav_list_7">
<li>
<xsl:if test="string-length($isTab7Other)>1 ">

<ul class="subnav_list">

<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title72" order="ascending"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:variable name="position" select="position()"/>
<xsl:if test="$titlelink='ComplexTab72' ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab72<xsl:value-of select="$position"/></xsl:attribute>
<xsl:value-of select="Title72"/>
</a>
</li>
</xsl:if>
</xsl:for-each>
</ul>
</xsl:if>
</li>
</ul>
</div>


<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title12" order="ascending"/>
<xsl:variable name="position" select="position()"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab11' or $titlelink = 'ComplexTab12' ">
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab11' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage1')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab111</xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab111" disable-output-escaping="yes"/>
<xsl:call-template name="Tab1instruction"></xsl:call-template>
<div id="clear"/>
</div>
</div>
</xsl:when>

<xsl:when test=" $titlelink = 'ComplexTab12' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage1')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab12<xsl:value-of select="$position"/></xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab121" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>
</xsl:choose>
</xsl:when>
</xsl:choose>

</xsl:for-each>


<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title22" order="ascending"/>
<xsl:variable name="position" select="position()"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab21' or $titlelink = 'ComplexTab22' ">
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab21' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage2')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab211</xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab211" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>

<xsl:when test=" $titlelink = 'ComplexTab22' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage2')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab22<xsl:value-of select="$position"/></xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab221" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>
</xsl:choose>
</xsl:when>
</xsl:choose>

</xsl:for-each>


<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title32" order="ascending"/>
<xsl:variable name="position" select="position()"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab31' or $titlelink = 'ComplexTab32' ">
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab31' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage3')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab311</xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab311" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>

<xsl:when test=" $titlelink = 'ComplexTab32' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage3')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab32<xsl:value-of select="$position"/></xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab321" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>
</xsl:choose>
</xsl:when>
</xsl:choose>

</xsl:for-each>


<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title42" order="ascending"/>
<xsl:variable name="position" select="position()"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab41' or $titlelink = 'ComplexTab42' ">
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab41' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage4')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab411</xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab411" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>

<xsl:when test=" $titlelink = 'ComplexTab42' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage4')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab42<xsl:value-of select="$position"/></xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab421" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>
</xsl:choose>
</xsl:when>
</xsl:choose>

</xsl:for-each>


<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title52" order="ascending"/>
<xsl:variable name="position" select="position()"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab51' or $titlelink = 'ComplexTab52' ">
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab51' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage5')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab511</xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab511" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>

<xsl:when test=" $titlelink = 'ComplexTab52' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage5')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab52<xsl:value-of select="$position"/></xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab521" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>
</xsl:choose>
</xsl:when>
</xsl:choose>

</xsl:for-each>


<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title62" order="ascending"/>
<xsl:variable name="position" select="position()"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab61' or $titlelink = 'ComplexTab62' ">
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab61' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage6')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab611</xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab611" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>

<xsl:when test=" $titlelink = 'ComplexTab62' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage6')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab62<xsl:value-of select="$position"/></xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab621" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>
</xsl:choose>
</xsl:when>
</xsl:choose>

</xsl:for-each>


<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title72" order="ascending"/>
<xsl:variable name="position" select="position()"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab71' or $titlelink = 'ComplexTab72' ">
<xsl:choose>

<xsl:when test=" $titlelink = 'ComplexTab71' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage7')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab711</xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab711" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>

<xsl:when test=" $titlelink = 'ComplexTab72' ">
<div>
<xsl:variable name="divclass" select="concat('portfolio_page_content ', 'examplePage7')"/>
<xsl:attribute name="class"><xsl:value-of select="$divclass"/></xsl:attribute>
<xsl:attribute name="id">ComplexTab72<xsl:value-of select="$position"/></xsl:attribute>

<div id="content_TOP" style="text-align: left;"/>

<div id="content" style="text-align: left;">
<xsl:value-of select="ComplexTab721" disable-output-escaping="yes"/>
<div id="clear"/>
</div>
</div>
</xsl:when>
</xsl:choose>
</xsl:when>
</xsl:choose>

</xsl:for-each>

</div>

<div id="vt_footer_bg">
<div id="portfolio_footer">This portfolio was created using the Virginia Tech ePortfolio System,
sponsored by Learning Technologies, Virginia Tech. 2210 Torgersen Hall,
Blacksburg, VA 24061-0292. eportfolio@....</div>
</div>
</div>
</div>

</div>
</body>
</html>
</xsl:template>


<xsl:template name="locateworkshowcase">
<xsl:variable name="mainmenu" select="concat($authoringPath, 'themeEPATVT/xml/workshowcasedropdowlist.xml')"/>
<xsl:variable name="xmlfile" select="document($mainmenu)"/>
<xsl:if test="$xmlfile=''">
<xsl:message terminate="yes">
Error: the menu.xml does not exist in portfolio admin site!
</xsl:message>
</xsl:if>
<xsl:variable name="categoryname">
<xsl:element name="item">
<xsl:for-each select="presentationProperties/portfolioOptiions/node()[contains(name(), 'ComplexTab')]">
<xsl:sort select="Title42" order="ascending"/>
<xsl:variable name="position" select="position()"/>
<xsl:variable name="titlelink" select="name(.)"/>
<xsl:if test="$titlelink='ComplexTab42' ">
<xsl:element name="portfolioOptiions">
<xsl:attribute name="value">

<xsl:value-of select="WorkshowcaseCategoryDropdownlist"/>
</xsl:attribute>
<xsl:attribute name="title">

<xsl:value-of select="Title42"/>
</xsl:attribute>
<xsl:attribute name="position">

<xsl:value-of select="$position"/>
</xsl:attribute>
</xsl:element>
</xsl:if>
</xsl:for-each>

</xsl:element>
<xsl:for-each select="xalan:nodeset($xmlfile)/element/enumeration">
<xsl:sort select="@value" order="ascending"/>
<xsl:variable name="thisCat" select="@value" />
<xsl:element name="item">
<xsl:attribute name="value">
<xsl:value-of select="$thisCat"/>
</xsl:attribute>
</xsl:element>
</xsl:for-each>
</xsl:variable>

<xsl:variable name="categorynamefull">
<xsl:variable name="optionsconent" select="xalan:nodeset($categoryname)/item[1]/portfolioOptiions"/>
<xsl:for-each select="xalan:nodeset($categoryname)/item">
<xsl:sort select="@value" order="ascending"/>
<xsl:variable name="thisCat" select="@value" />
<xsl:element name="item">
<xsl:attribute name="value">
<xsl:value-of select="$thisCat"/>
</xsl:attribute>
<xsl:element name="portfoliooption">
<xsl:copy-of select="$optionsconent"/>
</xsl:element>
</xsl:element>
</xsl:for-each>
</xsl:variable>

<xsl:for-each select="xalan:nodeset($categorynamefull)/item">
<xsl:sort select="@value" order="ascending"/>
<xsl:variable name="cat" select="@value"/>
<xsl:variable name="exsitcat">
<xsl:for-each select="portfoliooption/portfolioOptiions">
<xsl:sort select="title" order="ascending"/>
<xsl:variable name="value" select="@value"/>
<xsl:if test="$cat = $value ">
true
</xsl:if>
</xsl:for-each>
</xsl:variable>
<xsl:choose>
<xsl:when test="string-length($exsitcat) >1 and $cat !='Do not use a category' ">
<li>
<xsl:value-of select="@value"/>
<ul class="subnav_list">
<xsl:for-each select="portfoliooption/portfolioOptiions">
<xsl:sort select="title" order="ascending"/>
<xsl:variable name="value" select="@value"/>
<xsl:if test="$cat = $value ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab42<xsl:value-of select="@position"/></xsl:attribute>
<xsl:value-of select="@title"/>
</a>
</li>
</xsl:if>
</xsl:for-each>
</ul>
</li>
</xsl:when>
</xsl:choose>
</xsl:for-each>

<xsl:for-each select="xalan:nodeset($categorynamefull)/item[1]/portfoliooption/portfolioOptiions">
<xsl:sort select="title" order="ascending"/>
<xsl:variable name="value" select="@value"/>
<xsl:if test="$value = 'Do not use a category' ">
<li>
<a>
<xsl:attribute name="href">#ComplexTab42<xsl:value-of select="@position"/></xsl:attribute>
<xsl:value-of select="@title"/>
</a>
</li>
</xsl:if>
</xsl:for-each>

</xsl:template>

</xsl:stylesheet>
_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

test.JPG (228K) Download Attachment

Re: [Portfolio] Access to portfolios beyond graduation

2009-11-20T11:23:56Z

Re: [Portfolio] Access to portfolios beyond graduation I know a number of schools are starting to keep records in LDAP perpetually for things like alumni access, email, etc.

Admittedly, if you’re on AD or some other infrastructure where you pay licensing per-user – that can be unsustainable.

Jason

On 11/19/09 7:21 PM, "Susan Roig" <Susan.Roig@...> wrote:

If sign on is authenticated through LDAP and the student is removed after graduation how does graduate log in?

From: portfolio-bounces@... on behalf of Ackerman, Erica
Sent: Thu 11/19/2009 10:44 AM
To: Zaldivar, Marc; portfolio@...
Subject: Re: [Portfolio] Access to portfolios beyond graduation

In my understanding, the University of Michigan has instituted a policy where students continue to have editing access to Sakai after graduation in perpetuity. This change was made specifically at the request of the portfolio project.

Erica

-----Original Message-----
From: portfolio-bounces@... [portfolio-bounces@...] On Behalf Of Zaldivar, Marc
Sent: Thursday, November 19, 2009 8:16 AM
To: portfolio@...
Subject: Re: [Portfolio] Access to portfolios beyond graduation

Nancy,

Thank you for starting this thread. Your questions are mine too!

This is probably our most common workshop question from faculty, especially graduate faculty. We are trying to organize a plan with our Alumni group to think through the issues of access, but haven't made a lot of headway yet. Right now, we tell the students/faculty two things:

1. Before the students graduate, the portfolios they create can be downloaded and moved to an external webspace. (Unfortunately, the "download" button is not very reliable many times, but "Save Page As..." from the browser usually works for us.)
2. We do not really delete anything from the system currently. We encourage a self-cleaning policy, and because portfolios are aligned many times for assessment, we're leaving most things (sites, files, etc.) for a life cycle of potentially 7-10 years. (Of course we're only just beginning, so who knows? :-) In that scenario, the presentations students create, if made public, will exist for static display. They wouldn't be able to login to change them, but the URL should still be active. They could still show off that portion of their work, perhaps linking it into a new portfolio created in another space...

However, I'm not really happy with that. I'd love to hear from others about how they have approached this issue. Ideally, I'd love to see a model where we could have alumni pay for access to a running instance of OSP where they could continue to build and grow their portfolios.

Also, a side issue, but related. I was really happy to see the collaborative portfolio functionality come to fruition so quickly. It's a really important feature that several of our groups will be anxious to try out (I think we'll be upgrading this summer). However, I can envision this scenario on our campus. We have several leadership organizations or service learning groups that are interested in using the collaborative portfolio structure to reflect collectively on and demonstrate development of their community work, for one example. As I understand it currently, if Student A starts the collaborative portfolio, she is the "owner" and can invite others into it to help build it. When Student A graduates, how does she move ownership over to Student Q, the upcoming sophomore in the group? I suppose it could be done manually, by copying the forms in the interaction folder over to Student Q and having him rebuild it and start up a new one, but that would change the exist

ing URL... I suppose it could just live in Student A's account, for Student Q to take it over as main collaborator, but that could get messy after a few generations I'd imagine. Any ideas before we begin designing these projects?

Marc

On 11/18/09 4:42 PM, "Nancy O'Laughlin" <nolaug@...> wrote:

We have had several requests from faculty to continue student portfolio
access beyond graduation for viewing and editing. I was wondering how
other institutions handle this. Could you let me know what policies you
have in place or are considering? Are there any particular issues
involved with giving extended access to students?
Thanks,
Nancy

--
Nancy J. O'Laughlin, Ed.D.
IT-Client Support & Services, University of Delaware
030 Smith Hall, 18 Amstel Avenue
Newark, DE 19716
nolaug@... 302.831.0737

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"
_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

--
Jason Shao
Director of Product Development
CampusEAI Consortium
1940 East 6th Street, 11th Floor
Cleveland, OH 44114
Tel: 216.589.9626x249
Fax: 216.589.9639

Your input is important to improve upon our continuous efforts to service you better. Please e-mail my manager at anjli_jain@... with any feedback.

CONFIDENTIALITY NOTICE:
This e-mail together with any attachments is proprietary and confidential; intended for only the recipient(s) named above and may contain information that is privileged. You should not retain, copy or use this e-mail or any attachments for any purpose, or disclose all or any part of the contents to any person. Any views or opinions expressed in this e-mail are those of the author and do not represent those of CampusEAI Consortium or the Open Student Television Network. If you have received this e-mail in error, or are not the named recipient(s), you are hereby notified that any review, dissemination, distribution or copying of this communication is prohibited by the sender and to do so might constitute a violation of the Electronic Communications Privacy Act, 18 U.S.C. section 2510-2521. Please immediately notify the sender and delete this e-mail and any attachments from your computer. Warning: Although precautions have been taken to make sure no viruses are present in this e-mail, the companies cannot accept responsibility for any loss or damage that arise from the use of this e-mail or attachments.

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

2009-11-20T09:35:17Z

On Fri, Nov 20, 2009 at 11:56 AM, Maurer, Christopher Wayne <chmaurer@...> wrote:

The only difference I see is that Sean's import uses a full url to the xsl file while Erica's is just a path to a content resource.

Not sure if that makes a difference or not, but worth noting!

Chris

On Nov 20, 2009, at 11:34 AM, Ackerman, Erica wrote:

Sean,

We use xsl:import in the Page Composer, and it works in 2.6 and 2.5 both.

For example:

<xsl:stylesheet version="1.0" xmlns="http://www.w3.org/1999/xhtml" xmlns:sakaifn="org.sakaiproject.metaobj.utils.xml.XsltFunctions" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:osp="http://www.osportfolio.org/OspML" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xsl:output method="html" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
    <xsl:import href="/group/PortfolioAdmin/authoring/xsl/formCreate-wysiwyg.xsl" />

Could there be something wrong with the imported file?

Erica

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 10:33 AM
To: hongbo zhang
Cc: osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

I wonder if this is a 2.6-only issue.
Have you tried your template in a 2.6 instance?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Thu, Nov 19, 2009 at 3:41 PM, hongbo zhang <hbzhang@...> wrote:

I just tried using xsl:include. It works great.

I attached the sample file.

This is the template xsl file used in single form template. I include another xsl file, which has several templates. I just try to call it           <xsl:call-template name="Tab1instruction"></xsl:call-template> at line 743.

It seems it works fine for me. We run 2.5.4 instance.

Hongbo

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Thursday, November 19, 2009 3:10 PM
To: osp
Subject: [Portfolio] 503 for DTD request in templated portfolios that import other templates

Has anyone developed a portfolio template using an xsl file that imports other xsl files?
Like this:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">


<xsl:import href="http://yourserver.edu/path/to/your/imported.xsl"/>

   <xsl:template match="/">
     <xsl:text>Hey there!</xsl:text>
   </xsl:template>

</xsl:stylesheet>

When I do, I get a 503 error in the logs related to DTD issues.

I wrote it up as http://jira.sakaiproject.org/browse/SAK-17423.
It seems like it is similar to the stack trace that was occurring in free form portfolios in http://jira.sakaiproject.org/browse/SAK-16536.

This is 2-6-x branch r69087.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

2009-11-20T09:24:28Z

Sorry, you’re right, it’s in a form, not a portfolio template.

Erica

From: sean@... [mailto:sean@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 12:24 PM
To: Maurer, Christopher Wayne
Cc: Ackerman, Erica; hongbo zhang; osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

That import happens in a form though. Right, Erica?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Fri, Nov 20, 2009 at 11:56 AM, Maurer, Christopher Wayne <chmaurer@...> wrote:

The only difference I see is that Sean's import uses a full url to the xsl file while Erica's is just a path to a content resource.

Not sure if that makes a difference or not, but worth noting!

Chris

On Nov 20, 2009, at 11:34 AM, Ackerman, Erica wrote:

Sean,

We use xsl:import in the Page Composer, and it works in 2.6 and 2.5 both.

For example:

<xsl:stylesheet version="1.0" xmlns="http://www.w3.org/1999/xhtml" xmlns:sakaifn="org.sakaiproject.metaobj.utils.xml.XsltFunctions" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:osp="http://www.osportfolio.org/OspML" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xsl:output method="html" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
    <xsl:import href="/group/PortfolioAdmin/authoring/xsl/formCreate-wysiwyg.xsl" />

Could there be something wrong with the imported file?

Erica

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 10:33 AM
To: hongbo zhang
Cc: osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

I wonder if this is a 2.6-only issue.
Have you tried your template in a 2.6 instance?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Thu, Nov 19, 2009 at 3:41 PM, hongbo zhang <hbzhang@...> wrote:

I just tried using xsl:include. It works great.

I attached the sample file.

This is the template xsl file used in single form template. I include another xsl file, which has several templates. I just try to call it           <xsl:call-template name="Tab1instruction"></xsl:call-template> at line 743.

It seems it works fine for me. We run 2.5.4 instance.

Hongbo

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Thursday, November 19, 2009 3:10 PM
To: osp
Subject: [Portfolio] 503 for DTD request in templated portfolios that import other templates

Has anyone developed a portfolio template using an xsl file that imports other xsl files?
Like this:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">


<xsl:import href="http://yourserver.edu/path/to/your/imported.xsl"/>

   <xsl:template match="/">
     <xsl:text>Hey there!</xsl:text>
   </xsl:template>

</xsl:stylesheet>

When I do, I get a 503 error in the logs related to DTD issues.

I wrote it up as http://jira.sakaiproject.org/browse/SAK-17423.
It seems like it is similar to the stack trace that was occurring in free form portfolios in http://jira.sakaiproject.org/browse/SAK-16536.

This is 2-6-x branch r69087.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

2009-11-20T09:24:23Z

That import happens in a form though. Right, Erica?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Fri, Nov 20, 2009 at 11:56 AM, Maurer, Christopher Wayne <chmaurer@...> wrote:

The only difference I see is that Sean's import uses a full url to the xsl file while Erica's is just a path to a content resource.

Not sure if that makes a difference or not, but worth noting!

Chris

On Nov 20, 2009, at 11:34 AM, Ackerman, Erica wrote:

Sean,

We use xsl:import in the Page Composer, and it works in 2.6 and 2.5 both.

For example:

<xsl:stylesheet version="1.0" xmlns="http://www.w3.org/1999/xhtml" xmlns:sakaifn="org.sakaiproject.metaobj.utils.xml.XsltFunctions" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:osp="http://www.osportfolio.org/OspML" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xsl:output method="html" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
    <xsl:import href="/group/PortfolioAdmin/authoring/xsl/formCreate-wysiwyg.xsl" />

Could there be something wrong with the imported file?

Erica

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 10:33 AM
To: hongbo zhang
Cc: osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

I wonder if this is a 2.6-only issue.
Have you tried your template in a 2.6 instance?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Thu, Nov 19, 2009 at 3:41 PM, hongbo zhang <hbzhang@...> wrote:

I just tried using xsl:include. It works great.

I attached the sample file.

This is the template xsl file used in single form template. I include another xsl file, which has several templates. I just try to call it           <xsl:call-template name="Tab1instruction"></xsl:call-template> at line 743.

It seems it works fine for me. We run 2.5.4 instance.

Hongbo

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Thursday, November 19, 2009 3:10 PM
To: osp
Subject: [Portfolio] 503 for DTD request in templated portfolios that import other templates

Has anyone developed a portfolio template using an xsl file that imports other xsl files?
Like this:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">


<xsl:import href="http://yourserver.edu/path/to/your/imported.xsl"/>

   <xsl:template match="/">
     <xsl:text>Hey there!</xsl:text>
   </xsl:template>

</xsl:stylesheet>

When I do, I get a 503 error in the logs related to DTD issues.

I wrote it up as http://jira.sakaiproject.org/browse/SAK-17423.
It seems like it is similar to the stack trace that was occurring in free form portfolios in http://jira.sakaiproject.org/browse/SAK-16536.

This is 2-6-x branch r69087.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

2009-11-20T08:56:07Z

The only difference I see is that Sean's import uses a full url to the xsl file while Erica's is just a path to a content resource.

Not sure if that makes a difference or not, but worth noting!

Chris

On Nov 20, 2009, at 11:34 AM, Ackerman, Erica wrote:

Sean,

We use xsl:import in the Page Composer, and it works in 2.6 and 2.5 both.

For example:

<xsl:stylesheet version="1.0" xmlns="http://www.w3.org/1999/xhtml" xmlns:sakaifn="org.sakaiproject.metaobj.utils.xml.XsltFunctions" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:osp="http://www.osportfolio.org/OspML" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xsl:output method="html" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
    <xsl:import href="/group/PortfolioAdmin/authoring/xsl/formCreate-wysiwyg.xsl" />

Could there be something wrong with the imported file?

Erica

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 10:33 AM
To: hongbo zhang
Cc: osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

I wonder if this is a 2.6-only issue.
Have you tried your template in a 2.6 instance?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Thu, Nov 19, 2009 at 3:41 PM, hongbo zhang <hbzhang@...> wrote:
I just tried using xsl:include. It works great.

I attached the sample file.

This is the template xsl file used in single form template. I include another xsl file, which has several templates. I just try to call it           <xsl:call-template name="Tab1instruction"></xsl:call-template> at line 743.

It seems it works fine for me. We run 2.5.4 instance.

Hongbo

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Thursday, November 19, 2009 3:10 PM
To: osp
Subject: [Portfolio] 503 for DTD request in templated portfolios that import other templates

Has anyone developed a portfolio template using an xsl file that imports other xsl files?
Like this:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">


<xsl:import href="http://yourserver.edu/path/to/your/imported.xsl"/>

   <xsl:template match="/">
     <xsl:text>Hey there!</xsl:text>
   </xsl:template>

</xsl:stylesheet>

When I do, I get a 503 error in the logs related to DTD issues.

I wrote it up as http://jira.sakaiproject.org/browse/SAK-17423.
It seems like it is similar to the stack trace that was occurring in free form portfolios in http://jira.sakaiproject.org/browse/SAK-16536.

This is 2-6-x branch r69087.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

smime.p7s (3K) Download Attachment

Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

2009-11-20T08:34:00Z

Sean,

We use xsl:import in the Page Composer, and it works in 2.6 and 2.5 both.

For example:

<xsl:stylesheet version="1.0" xmlns="http://www.w3.org/1999/xhtml" xmlns:sakaifn="org.sakaiproject.metaobj.utils.xml.XsltFunctions" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:osp="http://www.osportfolio.org/OspML" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xsl:output method="html" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
<xsl:import href="/group/PortfolioAdmin/authoring/xsl/formCreate-wysiwyg.xsl" />

Could there be something wrong with the imported file?

Erica

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Friday, November 20, 2009 10:33 AM
To: hongbo zhang
Cc: osp
Subject: Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

I wonder if this is a 2.6-only issue.
Have you tried your template in a 2.6 instance?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Thu, Nov 19, 2009 at 3:41 PM, hongbo zhang <hbzhang@...> wrote:

I just tried using xsl:include. It works great.

I attached the sample file.

This is the template xsl file used in single form template. I include another xsl file, which has several templates. I just try to call it <xsl:call-template name="Tab1instruction"></xsl:call-template> at line 743.

It seems it works fine for me. We run 2.5.4 instance.

Hongbo

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Thursday, November 19, 2009 3:10 PM
To: osp
Subject: [Portfolio] 503 for DTD request in templated portfolios that import other templates

Has anyone developed a portfolio template using an xsl file that imports other xsl files?
Like this:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">


<xsl:import href="http://yourserver.edu/path/to/your/imported.xsl"/>

   <xsl:template match="/">
     <xsl:text>Hey there!</xsl:text>
   </xsl:template>

</xsl:stylesheet>

When I do, I get a 503 error in the logs related to DTD issues.

I wrote it up as http://jira.sakaiproject.org/browse/SAK-17423.
It seems like it is similar to the stack trace that was occurring in free form portfolios in http://jira.sakaiproject.org/browse/SAK-16536.

This is 2-6-x branch r69087.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates

2009-11-20T07:33:08Z

I wonder if this is a 2.6-only issue.
Have you tried your template in a 2.6 instance?

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

On Thu, Nov 19, 2009 at 3:41 PM, hongbo zhang <hbzhang@...> wrote:

I just tried using xsl:include. It works great.

I attached the sample file.

This is the template xsl file used in single form template. I include another xsl file, which has several templates. I just try to call it           <xsl:call-template name="Tab1instruction"></xsl:call-template> at line 743.

It seems it works fine for me. We run 2.5.4 instance.

Hongbo

From: portfolio-bounces@... [mailto:portfolio-bounces@...] On Behalf Of Sean Keesler
Sent: Thursday, November 19, 2009 3:10 PM
To: osp
Subject: [Portfolio] 503 for DTD request in templated portfolios that import other templates

Has anyone developed a portfolio template using an xsl file that imports other xsl files?
Like this:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">


<xsl:import href="http://yourserver.edu/path/to/your/imported.xsl"/>

   <xsl:template match="/">
     <xsl:text>Hey there!</xsl:text>
   </xsl:template>

</xsl:stylesheet>

When I do, I get a 503 error in the logs related to DTD issues.

I wrote it up as http://jira.sakaiproject.org/browse/SAK-17423.
It seems like it is similar to the stack trace that was occurring in free form portfolios in http://jira.sakaiproject.org/browse/SAK-16536.

This is 2-6-x branch r69087.

Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler@...

Re: [Portfolio] Access to portfolios beyond graduation

2009-11-19T17:16:04Z

U-M uses Cosign/Kerberos for authentication and access provisioning (not LDAP). Student accounts, called "uniqnames" do not expire upon graduation, so as long as someone doesn't actively change the sites/services that a former student/new alum has access to at graduation, those access privileges remain intact indefinitely.

SMD

On Nov 19, 2009, at 7:21 PM, Susan Roig wrote:

If sign on is authenticated through LDAP and the student is removed after graduation how does graduate log in?

From: portfolio-bounces@... on behalf of Ackerman, Erica
Sent: Thu 11/19/2009 10:44 AM
To: Zaldivar, Marc; portfolio@...
Subject: Re: [Portfolio] Access to portfolios beyond graduation

In my understanding, the University of Michigan has instituted a policy where students continue to have editing access to Sakai after graduation in perpetuity. This change was made specifically at the request of the portfolio project.

Erica

-----Original Message-----
From: portfolio-bounces@... [portfolio-bounces@...] On Behalf Of Zaldivar, Marc
Sent: Thursday, November 19, 2009 8:16 AM
To: portfolio@...
Subject: Re: [Portfolio] Access to portfolios beyond graduation

Nancy,

Thank you for starting this thread. Your questions are mine too!

This is probably our most common workshop question from faculty, especially graduate faculty. We are trying to organize a plan with our Alumni group to think through the issues of access, but haven't made a lot of headway yet. Right now, we tell the students/faculty two things:

1. Before the students graduate, the portfolios they create can be downloaded and moved to an external webspace. (Unfortunately, the "download" button is not very reliable many times, but "Save Page As..." from the browser usually works for us.)
2. We do not really delete anything from the system currently. We encourage a self-cleaning policy, and because portfolios are aligned many times for assessment, we're leaving most things (sites, files, etc.) for a life cycle of potentially 7-10 years. (Of course we're only just beginning, so who knows? :-) In that scenario, the presentations students create, if made public, will exist for static display. They wouldn't be able to login to change them, but the URL should still be active. They could still show off that portion of their work, perhaps linking it into a new portfolio created in another space...

However, I'm not really happy with that. I'd love to hear from others about how they have approached this issue. Ideally, I'd love to see a model where we could have alumni pay for access to a running instance of OSP where they could continue to build and grow their portfolios.

Also, a side issue, but related. I was really happy to see the collaborative portfolio functionality come to fruition so quickly. It's a really important feature that several of our groups will be anxious to try out (I think we'll be upgrading this summer). However, I can envision this scenario on our campus. We have several leadership organizations or service learning groups that are interested in using the collaborative portfolio structure to reflect collectively on and demonstrate development of their community work, for one example. As I understand it currently, if Student A starts the collaborative portfolio, she is the "owner" and can invite others into it to help build it. When Student A graduates, how does she move ownership over to Student Q, the upcoming sophomore in the group? I suppose it could be done manually, by copying the forms in the interaction folder over to Student Q and having him rebuild it and start up a new one, but that would change the exist

ing URL... I suppose it could just live in Student A's account, for Student Q to take it over as main collaborator, but that could get messy after a few generations I'd imagine. Any ideas before we begin designing these projects?

Marc

On 11/18/09 4:42 PM, "Nancy O'Laughlin" <nolaug@...> wrote:

We have had several requests from faculty to continue student portfolio
access beyond graduation for viewing and editing. I was wondering how
other institutions handle this. Could you let me know what policies you
have in place or are considering? Are there any particular issues
involved with giving extended access to students?
Thanks,
Nancy

--
Nancy J. O'Laughlin, Ed.D.
IT-Client Support & Services, University of Delaware
030 Smith Hall, 18 Amstel Avenue
Newark, DE 19716
nolaug@... 302.831.0737

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"
_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"
_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

SMD.

==========================================================

Sean DeMonner, IT Senior Project Manager, CTools Implementation Group

Digital Media Commons @ The Duderstadt Center, U-M (734) 615-9765

Pub Key 24DD6B09

Re: [Portfolio] Access to portfolios beyond graduation

2009-11-19T16:21:33Z

Re: [Portfolio] Access to portfolios beyond graduation

If sign on is authenticated through LDAP and the student is removed after graduation how does graduate log in?

From: portfolio-bounces@... on behalf of Ackerman, Erica
Sent: Thu 11/19/2009 10:44 AM
To: Zaldivar, Marc; portfolio@...
Subject: Re: [Portfolio] Access to portfolios beyond graduation

In my understanding, the University of Michigan has instituted a policy where students continue to have editing access to Sakai after graduation in perpetuity. This change was made specifically at the request of the portfolio project.

Erica

-----Original Message-----
From: portfolio-bounces@... [portfolio-bounces@...] On Behalf Of Zaldivar, Marc
Sent: Thursday, November 19, 2009 8:16 AM
To: portfolio@...
Subject: Re: [Portfolio] Access to portfolios beyond graduation

Nancy,

Thank you for starting this thread. Your questions are mine too!

This is probably our most common workshop question from faculty, especially graduate faculty. We are trying to organize a plan with our Alumni group to think through the issues of access, but haven't made a lot of headway yet. Right now, we tell the students/faculty two things:

1. Before the students graduate, the portfolios they create can be downloaded and moved to an external webspace. (Unfortunately, the "download" button is not very reliable many times, but "Save Page As..." from the browser usually works for us.)
2. We do not really delete anything from the system currently. We encourage a self-cleaning policy, and because portfolios are aligned many times for assessment, we're leaving most things (sites, files, etc.) for a life cycle of potentially 7-10 years. (Of course we're only just beginning, so who knows? :-) In that scenario, the presentations students create, if made public, will exist for static display. They wouldn't be able to login to change them, but the URL should still be active. They could still show off that portion of their work, perhaps linking it into a new portfolio created in another space...

However, I'm not really happy with that. I'd love to hear from others about how they have approached this issue. Ideally, I'd love to see a model where we could have alumni pay for access to a running instance of OSP where they could continue to build and grow their portfolios.

Also, a side issue, but related. I was really happy to see the collaborative portfolio functionality come to fruition so quickly. It's a really important feature that several of our groups will be anxious to try out (I think we'll be upgrading this summer). However, I can envision this scenario on our campus. We have several leadership organizations or service learning groups that are interested in using the collaborative portfolio structure to reflect collectively on and demonstrate development of their community work, for one example. As I understand it currently, if Student A starts the collaborative portfolio, she is the "owner" and can invite others into it to help build it. When Student A graduates, how does she move ownership over to Student Q, the upcoming sophomore in the group? I suppose it could be done manually, by copying the forms in the interaction folder over to Student Q and having him rebuild it and start up a new one, but that would change the exist

ing URL... I suppose it could just live in Student A's account, for Student Q to take it over as main collaborator, but that could get messy after a few generations I'd imagine. Any ideas before we begin designing these projects?

Marc

On 11/18/09 4:42 PM, "Nancy O'Laughlin" <nolaug@...> wrote:

We have had several requests from faculty to continue student portfolio
access beyond graduation for viewing and editing. I was wondering how
other institutions handle this. Could you let me know what policies you
have in place or are considering? Are there any particular issues
involved with giving extended access to students?
Thanks,
Nancy

--
Nancy J. O'Laughlin, Ed.D.
IT-Client Support & Services, University of Delaware
030 Smith Hall, 18 Amstel Avenue
Newark, DE 19716
nolaug@... 302.831.0737

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"

_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"
_______________________________________________
portfolio mailing list
portfolio@...
http://collab.sakaiproject.org/mailman/listinfo/portfolio

TO UNSUBSCRIBE: send email to portfolio-unsubscribe@... with a subject of "unsubscribe"