[Portfolio] Slow-downs

[Noah Botimer]

I think that the search scope becomes insignificant with a more tuned  
implementation. The selection criteria for portfolio assembly are  
owner and form type. The selection criterion for updating a schema is  
form type only. Presently, neither of these is available for  
efficient filtering, which is the core problem. We use two different  
strategies to cut down the set size as best as we can, but both still  
end up searching for and processing far too many irrelevant forms.

A toggle between the current implementation and My Workspace  
searching in the portfolio assembly screen only would be reasonable  
until a better implementation is completed.

Thanks,
-Noah

On May 20, 2009, at 4:07 PM, Sean Keesler wrote:

> Do you think that two different solutions optimized for each of the
> scenarios might be optimal?
>
> Sean
>
>
>
> On Wed, May 20, 2009 at 4:03 PM, Noah Botimer <botimer at umich.edu>  
> wrote:
>> Learners don't, typically. Anyone who owns a form definition needs  
>> to be
>> able to, though (updating schemas). This is also relevant to  
>> reporting
>> capabilities.
>>
>> To be more specific, I'm not saying that finding in My Workspace  
>> isn't
>> appropriate to nominal use. I'm saying that we should avoid the  
>> redefinition
>> of the technical problem/capability to minimize one variable. The  
>> problem
>> here is that the mechanism for finding forms has gross scale  
>> problems in
>> multiple dimensions. We're examining a couple of rather simple  
>> strategies
>> that address them all and don't change the behavior. My base  
>> metric is that
>> the user should see the portfolio screens in no more than 3  
>> seconds, and I
>> think that is readily achievable at scale.
>>
>> Thanks,
>> -Noah
>>
>> On May 20, 2009, at 3:09 PM, Sean Keesler wrote:
>>
>>> When does a normal end user really have to find all forms of a type
>>> everywhere?
>>>
>>> Sean
>>>
>>>
>>
>
>