Monk Proxy Call
11 March 2008

James, Matt, Amit, Stan, Stéfan, Andrew, Catherine, Alejandro

Catherine has provided feedback on the current version.
April hackfest. Will we do that and where?
The system isn't currently in a state to support a user meeting, but can it be ready in a month?

The main things remaining to do:

• more tools
• the analysis calls
• look and feel

We have the analysis calls, earlier on MONK proxy and now on the MONK middleware, listed as the 3 SEASR calls. There is documentation on the wiki.

We should have that ready by end of Thurs.

Proxy calls remaining to do:

1. The confidence values are currently faked up.
2. We also still don't have a featurelist: there isn't a call yet.
3. We should be able to click on a feature, and the system will mark which works have that feature. You can also see those items marked in the document, and multiple items were possible.

What would users want to have:

• Sara and Kirsten could both use Search by Example.
• Tanya and Kirsten could use Clustering.
• All could use some visualization.

Can we have an interim hackfest for the programmers? We could tie up some loose ends before they meet:

• Google Charts. These are in MONK proxy but not in interface yet. Mike should talk with Andrew about setting up the component.
• Search and advanced search.
• Export to ManyEyes. We should assign this to Mike P after he finishes the Google Charts.

Possible programmer hackfest participants:
• Andrew, Alejandro, Matt, Mike P., and Amit

This would be helpful if people were able to finish their current assignments soon.

Catherine has a Workbench Implementation page that lists who is working on what and when. We should also start to make proper use of the Jira tickets, for assignment and tracking.

Matt was working on dynamically loading components. This needs to be documented: using the Jira tickets would be helpful. He will start today.

Alejandro has been working on search and advanced search: there is GetWorksContainingFeature, for example, documented on the wiki under Monk proxy calls. He's been in touch with Andrew. Timeline roughly a week.

Amit will be away the week of Sun March 16 to Fri March 21.

In the Analysis calls, we currently have spelling and lemma. But some of the other options are still under development in SEASR, such as stopwords and stemming. These currently require custom workflows for each one. Maybe two weeks.

Jira ticket state:
• in progress means someone has started on it;
• open means someone is assigned but hasn't started yet.

If it is a bug, we will add a ticket. If it is a discussion item, we should post it to the list.

Can we make a bi-weekly or weekly call at 10:00 EST on Tuesdays for interface design discussions?

Maybe we should assign some clearer deadlines. Deadlines, even fairly arbitrary ones, sometimes help structure the work.

We will have a Skype call tomorrow (Wed) on the current design roadblocks that Andrew has identified.

Stan will write to John to inquire about the April hackfest logistics.

Jira tickets should if possible include screenshots.