[Digir-dev] catching up

[P.J. S. <pschwartz@CalAcademy.org>]

hey dave (and friends),

its been a while since we touched base so i just wanted to do so.  things
are coming along pretty nicely with the portal side of things.  i put
together a dynamic form that i'm fairly pleased with, from a functional
perspective, for the initial portal.  i've also hooked up the engine layer
with the presentation layer, at least for the "asking" side of queries.  i
figure we need to settle up some details that were discussed earlier and
wondered if you, dave, have made any headway on them already.  here are
the things i'm thinking about:

1. your last email outlined some functionality in regards to asking for
metadata.  to refresh, you suggested one asks for metadata in the regular
query structure where the dbName is "resources" and the filter is left
blank.  (i do recall you suggested that if dbName was blank, the default
would be to get metadata.  i'm not sure i agree with the idea here, but
its a minor detail).  is your thinking, and programming, still in line
with these ideas?

2. do you have a schema, or example, of what the returned metadata
structure is?  i looked at the EML stuff and from what i could quickly
glean, its beyond the scope of what we are ready for.  i figure we should
start with a really simple, basic structure for now.  have you one
already?  i'm anxious to add in the querying and storing of metadata bit
to the portal layer.

3. also, stan and i spoke briefly about the incomplete darwin core v. 2
schema and your mention of this.  any thoughts on what to hammer out next
with it.

4. lastly, we probably need to nail down the diagnostics messages and add
them to the protocol schema, or a separate schema.  i myself, will have to
sort them out from my code as error handling is cleaned up/finalized.

anything else on your mind dave?

hope all is well.  happy new year, btw.  :)

peej