2013-04-01 escrum

Scruminess

What have you done since the previous call?
- Scott - no activity
- Marie - Fixed CO545, closed CO428, made a commit for CO139.

What are you planning to do between now and the next call?
- Scott - grouper training @ CalTech
- Marie - Finish open tickets. Maybe CO533.

Any impediments/stumbling blocks?
- Scott - time availability should start easing up soon and work will restart on comanage items
- Marie - We should talk about what type of searching is really needed in what situations/pages. Also, in looking at CO-392, I'm getting some "Not Implemented" error messages.

What are you planning to do between now and the next call?
- Benn: getting back in to swing of work; will have more to report on Friday
- Heather: International call and coordination w/ SURFnet re: CoCoA demo

What have you done since the previous call?
- Scott: Grouper training with LIGO (not COmanage related); identified another immediate LIGO use case
- Marie: a few tickets related to searching and filtering for the UI, including CO-139, CO-209 and CO-497
- Benn: working on provisioning (CO-547) and it should be done in the next week

What are you planning to do between now and the next call?
- Scott: Probably no comanage work before Monday, but by the next dev call, will start looking at Jira tickets again
- Marie: depends on the discussion in the dev part
- Benn: more provisioning work

Any impediments/stumbling blocks?
- Scott: time
- Marie: need input
- Benn: will soon need to spend more time on I2 prep

Another instance of a common LIGO use case
- another instance of a use case where a LIGO group has external collaborators they want to work with; need to on-board them, get their ePPN, etc

Search issues and scaling
- Marie put in the search by attributes for org identities, but not sure exactly what is needed in the UI; we can do the filtering and use the same code for the search as you type function, and will need to add java script to allow the "as you type" part; what fields do we really need this for? What is the specific use case?
  - when someone is on-boarded, you want to check if someone is already in the system. Do we need the auto-complete for just names, or also for institution and everything? We already have the real time reconciliation/matching on some elements when you add a person via a petition, so we don't envision people looking through the full list manually, you would explore via the petition. this is more along the lines of "I need to find someone's record and fix something" so probably looking by name; there is also a use case for a LIGO manager who needs to search by institution or org name searching
  - Marie to send a snapshot of current appearance

CO 392 (CO Petition UI)
- in trying to enroll someone, Marie gets a "not implemented" error; in trying to go to a similar page to what's in the description of CO-392, cannot because she cannot create those
  - "Not implemented" should be throwing an exception and a stack trace; this will require digging through code

Virtual Working Group in May
- Scott and Heather are both unavailable, but Benn is available to do this
- Heather to help with the slides - here's what this project is about, here's what we did last year, here's what's rolling out this year, here's when it goes in to production at LIGO; maybe a small demo
- Benn to run the session