|
|
(5 intermediate revisions by 2 users not shown) |
Line 1: |
Line 1: |
− | ==NOTES== | + | =Working Information= |
| | | |
− | Overall goal is to get IMLS to see this set of capabilities as a fundamental piece of the evolving world of distributed metadata and aggregations. Builds on certain premises: substantial work has been done, research has been done and has been tested in a particular environment. It has more general utility. This is about generalizing the tool, and completing the work, distribution, documentation,etc.
| + | ==Meeting and Telecon AGENDAS & NOTES== |
| | | |
− | Proposal will need to address:
| + | [[12/12-13/05]] Meeting: Stuart, Diny, Diane & Jon (at Diane's house in Jacksonville) |
| | | |
− | What is generalization? How does the end result plug & play?
| + | [[10/15/05]] Meeting: Stuart and Diane (at Diane's house in Jacksonville) |
− | Where does UIUC IMLS fit in? Even without that, it needs to demonstrate how it works. GEM will be on instance (with or without the IMLS data)
| + | |
− | | + | |
− | Description of current components and where they are now
| + | |
− | Where we want to get them by the end
| + | |
− | Interactions with two repositories
| + | |
− | | + | |
− | Need match of 50% for more than $250,000
| + | |
− | If GEM/IMLS, will have some money
| + | |
− | If not leave at personnel expenses, some match with UW infrastructure
| + | |
− | If we keep it under $250,000, only at 1/3 match
| + | |
− | | + | |
− | <b>Action item:</b> See if Cornell will give back a portion of overhead if we're not doing anything but setting up and administering grant? Diane will ask Tom about this.
| + | |
− | | + | |
− | <b>Action item:</b> Stuart will check and see if they accept appendices, so we can include screenshots
| + | |
− | | + | |
− | NOTES:
| + | |
− | | + | |
− | Need bulleted list about who could use this tool (including traditional libraries who have a digital library/institutional repository component)
| + | |
− | | + | |
− | JP: Need more information about components, and what they do specifically (functions), plus a statement about what's still needed, what needs to be reconceptualized based on experience.
| + | |
− | Also:
| + | |
− | #Check overview and conceptual framework docs for missing pieces, if you need more detail do it on another page, don't loose conciseness.
| + | |
− | #Add bit about plugging into other user authentication systems
| + | |
− | #What are the implementing technologies for each piece and what do you envision as a 'new' implementation environment.
| + | |