Re: SIMILE PI phone conference, 15-Jan-04 1100 EDT/1600 BST

Unfortunately, I will not be able to make this meeting either. My hope 
is to spend some f2f time with some of the Simile team while I'm at 
MIT, but I'm afraid I'm double-booked for todays PI call.

Some comments below. David K, in particular I'd appreciate feedback on 
the Agenda item 6 re Haystack.

--
eric miller                              http://www.w3.org/people/em/
semantic web activity lead               http://www.w3.org/2001/sw/
w3c world wide web consortium            http://www.w3.org/


On Jan 14, 2004, at 2:47 PM, Butler, Mark wrote:

> SIMILE PI phone conference, 15-Jan-04 1100 EDT/1600 BST
>
> 866-639-4752 or +1-574-935-6705
> PIN: 2536617
>
> irc://irc.w3.org:6665/simile
>
> Agenda
>
> 1. Review demonstration goals
>
> 2. Review project task list
>
>    - round table on currently active tasks
>
>    - review non-active tasks
>
> (More details of these items are below)
>
>
> DEMONSTRATION GOALS
>
> Stage 1: Using subset of Artstor corpus, data in memory, demonstrate 
> that we
> can
>
> 1. view subset of Artstor data
> 2. view OCW data
> 3. use faceted browse on subset of Artstor data
> 4. use faceted browse on OCW data
> 5. query subset of Artstor data
> 6. query OCW data
> 7. do 1 & 2 together
> 8. do 3 & 4 together
> 9. do 5 & 6 together
>
> Stage 2: Repeat stages 1 - 9 but for the full Artstor corpus with the 
> data
> in persistant database
>
> Stage 3: Repeat stages 1 - 9 but for full Artstor corpus, retrieve 
> data via
> HTTP
>
>
> CURRENTLY ACTIVE TASKS
>
> 1 - Revising Artstor and OCW datasets (Mark)
> Progress: OCW uses Perl and XSLT. Unfortunately getting Perl to work 
> on my
> machine took nearly a day so little progress.
> Subtasks:
> 1.1 - Add type information to OCW
> 1.2 - Adopt a common way of displaying names in both Artstor and OCW
> 1.3 - Work on custom browser has highlighted that some of the fields in
> Artstor are hierarchical, need to change data model to reflect this and
> update browser
>
> 2 - Displaying Artstor and OCW datasets in Haystack (Steve, Vineet, 
> Mark)
> Progress: Can display Artstor data in Haystack (see enclosed 
> screenshot)

Excellent!


> Subtasks:
> 2.1 - Some issues about redraw speed in Haystack
> 2.2 - If you click on facet, then it no longer displays as a 
> collection but
> as a list of URIs
> 2.3 - want to be able to customise the fields in the facet navigator 
> as some
> contain technical metadata which we are excluding from the demo
> 2.4 - In Haystack, the faceted browser only identifies 984 items in the
> collection, whereas the custom browser has 3046 - why is this?
> 2.5 - Haystack also needs to address the hierarchical fields issue, 
> but it
> is less obvious here as this detail is swamped due to the technical 
> metadata
> 2.6 - Need to work on displaying OCW data, but this is waiting on the 
> OCW
> dataset
>
> 3 - Produce HTML front-end for Haystack (Steve)
> Progress: Steve
>
> 4 - Custom browser (Mark)
> Progress: Have made very good progress, now have a working prototype 
> that
> can browse Artstor data (see enclosed screenshot)

excellent! Looks good. Are there pointers available to the source code? 
Are you pairing with anyone at the moment on this development?

> Subtasks:
> 4.1 - Need to add paging for facets
> 4.2 - Need to add reordering of facets
> 4.3 - Need to add hierarchical grouping of facets, where appropriate
> 4.4 - Could add searching to facets
> 4.5 - Need to demonstrate OCW dataset in prototype
> 4.6 - Currently prototype uses lucene as a query engine. Need to 
> switch to
> using RDQL.
> 4.7 - Put prototype in CVS for team feedback
>
> 5 - CVS access for all team members (Mark)
> Progress: Mark has arranged CVS access for all team members
> Subtasks:
> 5.1 - Need to reorganize CVS in a more intelligent manner, make proper 
> build
> scripts
>
> 6 - Haystack Joseki Integration (Vineet, David H, Steve)
> "David H is gone till the end of the month. He managed to get the
> integration working, except that there where bugs - some views 
> displayed
> properly while others gave errors. We do not know the nature of the 
> bug, and
> I have a feeling that Dennis wanted to look at it. I might look at it 
> if I
> manage to finish the other things before then, i.e. not before the 
> last week
> of this month." Vineet

David K. please assess if this puts the Haystack demo at risk and 
coordinate with Mark B.

> NON-ACTIVE TASKS
>
> 7 - Haystack user testing
> Identify several team members to do this.
>
> 8 - Managing Haystack / SIMILE issue list
> Identify someone to manage this issue list.
>
> 9 - Identifying a subset of corpus for stage 1 demo
> Identify someone to do this
>
> 10 - Making datasets available via Joseki
> Two issues here: we need a process for doing this, as we will have to 
> update
> them, so need to make updates as simple as possible, and we need to do 
> this
> in a secure way.
> Identify someone to work on this
>
> 11 - Custom browser user testing
> Custom browser not yet finished, but when issues are resolved need to 
> make
> it available to team for user testing in the same way as Haystack. 
> Also need
> to manage issue list in a similar way.
>
> 12 - Exploring data using Brownsauce or RDFNavigator
> Proposed by Eric Miller

Making the data availiable (as you have) satisfys my concern. I hope to 
get access to this shortly.

> 13 - Creating infrastructure at simile.mit.edu
> Private email list, WIKI

re WIKI, I can offer http://esw.w3.org/topic/simile to get us started.  
I have to admit, I haven't gotten into  wiki's yet, but I'm more 
interested in supporting any means in which the developers are 
interested in collaborating.

--
eric miller                              http://www.w3.org/people/em/
semantic web activity lead               http://www.w3.org/2001/sw/
w3c world wide web consortium            http://www.w3.org/

Received on Thursday, 15 January 2004 08:46:15 UTC