Date

Attendees

Agenda -

To Do

CZO Extractors next

Individual Updates/Blocking


TimeItemWhoNotes

Walk thru In Review Items


BoxBen


Luigi

Story for CZO - won't be done by AGU Dec 9 - so no point in rushing

Work on this in Design Meeting on Monday

User Keys - working on PR - should be able to test soon



Rob/Yan

LDAP

Yan is ready to have Rob run the script

Need to make sure Sign Up points to the new LDAP sign up page - Kenton McHenry this is a link in what you have control of in the Brown dog site - you need to change the link to the LDAP signup page - (the identity page - NCSA identity page - https://identity.ncsa.illinois.edu/register/Y23A6Y536R)

We need to put some kind of Terms of Service on there? Do we keep same one for now that is in the NCSA page? We don't have anything for Group- need to decide? Before we turn on LDAP?

"we are not responsible for your data"



Yan

Pecan - Brown Dog user token

clarify implementation?

Is it configurable so they can turn it on and off?  Will all users have to use an individual login?

Per Yan - it is on the PHP - Yan will show

Username and Password is in config

Only if you want to use brown dog at that point of the workflow

Why don't we have them provide a key instead of a token (which expires every 24 hours)

Do token for now - call it Access token -

make a task to change R library to do key in the future

Do keys have names? we could - this is a pecan key

Yan has new plan for implementation: XXXXX


Status

http://browndog.ncsa.illinois.edu/status.html

This does not indicate if an extractor is down
clicking on the dot point - gives a big text page
http://browndog.ncsa.illinois.edu/report.html?id=5bfedba627f52878e09d6e64


do we want this exposed or should we just have a short list of what extractors are down?

Make a task to investigate how easy it would be to have the extractor name show with error and do we take away the big text page


Action items

  •  Tasks?