[Portfolio] Question about SAK-15822

Maurer, Christopher Wayne chmaurer at iupui.edu
Wed Mar 11 10:12:49 PDT 2009


Well, I can¹t really make that determination.  That¹d be up to Lynn and all
the other functional folks...

Chris


On 3/11/09 9:40 AM, "Beth Kirschner" <bkirschn at umich.edu> wrote:

> It seems that the behavior that is really desired is not to change the
> way 'Manage Status' works for all users, but to allow an initial
> status of "Pending" in addition to "Ready" and "Locked".
> 
> - Beth
> 
> On Mar 10, 2009, at 2:31 PM, Holladay, Bryan Andrew wrote:
> 
>> > I would not advise calling this bulk creation of user¹s matrices
>> > after creating the matrix, for this will guarantee a slowdown.  I
>> > believe if you trigger this only in the case where someone is
>> > changing the status of a cell and there are missing user matrices,
>> > then this off case wouldn¹t have a big impact since the majority of
>> > the use cases will not be a complete bulk update (just picking up
>> > stragglers like new users)
>> >
>> > Bryan
>> >
>> >
>> > On 3/10/09 2:29 PM, "Maurer, Christopher Wayne" <chmaurer at iupui.edu>
>> > wrote:
>> >
>> > That is correct.
>> >
>> > Chris
>> >
>> >
>> > On 3/10/09 2:25 PM, "Sean Keesler" <sean at keesler.org> wrote:
>> >
>> > Seems to me that this would be a time consuming operation *just
>> > once* (when the matrix is published and all the user instances are
>> > created) and that the performance after that would be no different
>> > than if everyone had actually used the matrix.
>> >
>> > Sean
>> >
>> >
>> > On Tue, Mar 10, 2009 at 1:53 PM, janice.smith <janice.smith at threecanoes.com
>>> > > wrote:
>> > Hi Chris
>> >
>> > I have not followed all the details of this discussion, but I can
>> > tell you from experience that performance issues with OSP can
>> > literally shut down an instance of Sakai. If we have the choice
>> > between creating something that dramatically complicates performance
>> > and something that does not, I will choose the less complicated
>> > option every time. So far the big performance problems have been
>> > with the wizard. If the matrix starts generating performance
>> > problems (which it has not to date), there will be serious
>> > consequences for portfolio implementations. Also as an FYI, at many
>> > institutions, only some of the users in portfolio sites actually use
>> > the matrix.
>> >
>> > Janice
>> >
>> > Janice A. Smith, Ph.D.
>> > Three Canoes Consulting
>> > 1204 Laurel Avenue
>> > Saint Paul, Minnesota 55104, USA
>> > 651-642-9069
>> > 207-841-6262 (cell)
>> > janice.smith at threecanoes.com
>> > jasmith at mm.com
>> >
>> >
>> > ---- On Tue, 10 Mar 2009 10:38:28 -0700 Christopher Wayne Maurer
>> <chmaurer at iupui.edu
>>> > > wrote ----
>> >
>> > http://bugs.sakaiproject.org/jira/browse/SAK-15822
>> >
>> >  As a brief summary, the ³manage status for all users² functionality
>> > will only work if the user has visited the matrix in question (and
>> > generated the actual data).
>> >
>> >  What do people think about having this trigger the creation of
>> > matrix data first?
>> >
>> >  My biggest concern is the performance of creating all that data (if
>> > it doesn¹t exist).  I would expect that the normal use case here is
>> > that most users will have interacted with their matrix by this point.
>> >  But, in practice this may not be the case.  I can obviously create
>> > a site with 1000 users, create a matrix, and immediately change the
>> > status for all users (not the same as changing the cell¹s initial
>> > status).  This action will create all 1000 user matrices (well, 999
>> > since the author just went to the matrix).
>> >
>> >  The case that isn¹t covered (and I think that it¹s okay not to
>> > worry about it) is when all the statuses have been changed and a
>> > user is added to the site.
>> >
>> >  So, what do people think about this bulk creation?
>> >
>> >  Chris
>> >  _______________________________________________
>> > portfolio mailing list
>> > portfolio at collab.sakaiproject.org
>> > http://collab.sakaiproject.org/mailman/listinfo/portfolio
>> >
>> > TO UNSUBSCRIBE: send email to portfolio-unsubscribe at collab.sakaiproject.org
>> >  with a subject of "unsubscribe"
>> >
>> >
>> > _______________________________________________
>> > portfolio mailing list
>> > portfolio at collab.sakaiproject.org
>> > http://collab.sakaiproject.org/mailman/listinfo/portfolio
>> >
>> > TO UNSUBSCRIBE: send email to portfolio-unsubscribe at collab.sakaiproject.org
>> >  with a subject of "unsubscribe"
>> >
>> >
>> >
>> > _______________________________________________
>> > portfolio mailing list
>> > portfolio at collab.sakaiproject.org
>> > http://collab.sakaiproject.org/mailman/listinfo/portfolio
>> >
>> > TO UNSUBSCRIBE: send email to portfolio-unsubscribe at collab.sakaiproject.org
>> >  with a subject of "unsubscribe"
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/portfolio/attachments/20090311/8583ad9b/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2141 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/portfolio/attachments/20090311/8583ad9b/attachment-0001.bin 


More information about the portfolio mailing list