Forwarding this to the list, I accidentally sent it from my other e-mail account and it got blocked.
Begin forwarded message: > From: Justin <[email protected]> > Date: January 5, 2010 9:04:04 AM EST > To: Svetoslav Nedkov <[email protected]> > Cc: Colin Clark <[email protected]>, Fluid Work > <[email protected]>, James William Yoon <[email protected]> > Subject: Re: My Collection question > > Hi Sveto, > > Happy New Year. > > I and some others here are planning to take a look at the work you've done on > My Collections this week. So we should have some feedback to you on that > shortly. > > I've cc'd James on this, as some of the questions you have may be better > answered by him. > > I've made some more comments below. > > Thanks > Justin > > On 2010-01-05, at 8:36 AM, Svetoslav Nedkov wrote: > >> >> Hello Justin and Colin, >> >> I'm done with another stage in the development of the user collections for >> Engage and some issues emerged that I'd like to discuss. >> >> 1. Joan wrote about this but it is also related to the user collections - >> how do we identify an user in Engage, will there be a login page or we will >> use some other mechanism to authenticate users? > > I believe the designers are still working on this one. > >> 2. One month ago we talked about shadow artifacts that will be created in >> the museum databases (see the summary from the developers meeting mailed to >> the list by Michelle). I've come to making use of them, but when we >> discussed things with our supervisor here it turned out that this redundancy >> can lead to issues when doing an update. An update will involve changing two >> documents and as we lack the means to do a transaction in CouchDB this could >> lead to some inconsistent data. So we have a suggestion to use CouchDB views >> for shadow artifacts that will simply aggregate documents and give access to >> them. This will result in the same ease of use while eliminating the risk of >> inconsistency. > > I may be slightly confused about the shadow documents. I think the idea was > to have two documents. One is what comes from the museum and the other being > what we write to. When the information is displayed it will pull from both > documents, but if anything is saved it will only go to the shadow document. > Is that the same as what you were mentioning here? I'm slightly foggy on > pre-holiday items, so others should probably weigh in on this. > >> Another thought about shadow artifacts - if they are represented by >> documents in the database will they be created by hand or on the fly when >> they are not present? >> >> Anyway I feel that this is a subject that needs to be cleared out further. >> >> 3. I think that the user collections need some paging functionality in order >> to present larger collections. Just need a confirmation. > > Another one for the designers to comment on. I think the current wireframes > have the page scrolling but depending on the size of the collection paging > may make more sense. I'm working on getting paging functionality working for > browse and artifact view so you should be able to use that if needed. You can > see the code here ( > http://source.fluidproject.org/svn/fluid/engage/fluid-engage-core/trunk/framework/js/engageClientUtils.js > ). It isn't quite finished yet, as you can't start off at any point inside > of the dataset yet, you always start on the first page. > >> 4. About the behaviour of the collect/uncollect links - I have made the >> collect link take the user to the My Collection page, while the uncollect >> link returns him to the browse artifacts page. I'll be glad to hear your >> opinions about that. > > The designers will likely have more thoughts on this. I did a quick look over > the wireframes and didn't notice any clear indication of behaviour related to > this, but i might have just missed it. Does this mean that you've added the > collect/uncollect button to the top nav bar on the artifact view page? > >> I'm hoping you will take the time to look into this and maybe we can talk >> about some of the issues on the developers' meeting. > > The dev meeting is probably a good place to continue this, although I imagine > there will be some discussion in this thread before hand as well. I think > Boyan is going to do a code walkthrough at that meeting, you could probably > do one also if you like. > >> >> Regards, >> Svetoslav _______________________________________________________ >> fluid-work mailing list - [email protected] >> To unsubscribe, change settings or access archives, >> see http://fluidproject.org/mailman/listinfo/fluid-work >
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
