http://wiki.metadataregistry.org/api.php?action=feedcontributions&user=208.31.47.161&feedformat=atomMetadata-Registry - User contributions [en]2024-03-29T09:32:12ZUser contributionsMediaWiki 1.22.6http://wiki.metadataregistry.org/F2F_Meeting,_4/27/06,_SeattleF2F Meeting, 4/27/06, Seattle2006-04-12T14:55:21Z<p>208.31.47.161: </p>
<hr />
<div>==Meeting Agenda and Notes, 4/27/06, Seattle==<br />
<br />
1. Planning for Metadata Management System integration with GEM data<br />
<br />
* Report on Wednesday meeting with Jon, Ryan, and Damon<br />
<br />
2. Diane and Jon's role in re-enabling GEM data collection and augmentation<br />
<br />
* Do we need a formal contract? If so, what are it's components?<br />
* Budget expectations?<br />
* Assistance needs?<br />
<br />
3. GEM cataloging/augmentation services<br />
<br />
* How will they operate?<br />
* Who will run them?</div>208.31.47.161http://wiki.metadataregistry.org/Apr._12,_2006Apr. 12, 20062006-04-10T19:25:20Z<p>208.31.47.161: </p>
<hr />
<div>== Telecon, Wednesday, April 12, 2006 ==<br />
<br />
1. Review [http://phoenix.ischool.washington.edu/wiki/index.php/Other_Meetings_and_Notes Agendas for 4/26-28/2006]<br />
<br />
2. Update on progress with the Registry (Jon)</div>208.31.47.161http://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-10T18:46:57Z<p>208.31.47.161: </p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
1. Presentation: Ryan Laundry<br />
<br />
* Technical overview of current GEM processes for ingesting and maintaining data<br />
* Review of Siderean capabilities and processes<br />
<br />
2. Presentation: Damon Gravning<br />
<br />
* Technical overview of current ASN processes for ingesting and maintaining data<br />
* Overview of tools used with schools<br />
<br />
3. Presentation: Jon Phipps<br />
<br />
* Metadata Management System requirements and functionality<br />
* Augmented Metadata requirements (with 'mudball' schema example)</div>208.31.47.161http://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-10T18:45:16Z<p>208.31.47.161: </p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
1. Presentation: Ryan Laundry<br />
<br />
* Technical overview of current GEM processes for ingesting and maintaining data<br />
* Review of Siderean capabilities and processes<br />
<br />
2. Presentation: Damon Gravning<br />
<br />
* Technical overview of current ASN processes for ingesting and maintaining data<br />
* Overview of tools used with schools<br />
<br />
3. Presentation: Jon Phipps<br />
<br />
* Metadata Management System requirements and functionality</div>208.31.47.161http://wiki.metadataregistry.org/Other_Meetings_and_NotesOther Meetings and Notes2006-04-10T18:21:55Z<p>208.31.47.161: </p>
<hr />
<div>[[F2F Meeting, 10/14/05, Ithaca]]<br />
<br />
[[Technical F2F Meeting, 4/26/06]]<br />
<br />
[[F2F Meeting, 4/27/06, Seattle]]<br />
<br />
[[F2F Meeting, 4/28/06, Seattle]]</div>208.31.47.161http://wiki.metadataregistry.org/F2F_Meeting,_4/28/06,_SeattleF2F Meeting, 4/28/06, Seattle2006-04-10T18:16:16Z<p>208.31.47.161: </p>
<hr />
<div>== Registry Project Meeting, Seattle, 4/28/06==<br />
<br />
1. Review of current work and progress<br />
<br />
* Infrastructure, interfaces, data, testing<br />
* Plans for demo to DC UB<br />
<br />
2. General open questions and issues:<br />
<br />
* How do we deal with the Super Properties? For instance, do we allow people to add things labelled as "Notes" or do we require them to choose among the subproperties (definition, changeNote, etc.)<br />
* Is historyNote a good place to put term sources, such as we've defined in the NSDL Learning Resource Type vocabulary? We're thinking that the use of skos:inScheme should wait until we do term mapping.<br />
* In the NSDL vocabularies, we've listed the sources of definitions but there's no place to put those in skos. We're thinking it might be a something we should propose?<br />
<br />
3. Versioning issues:<br />
<br />
* Melanie's paper on Versioning<br />
* Differences between "history" and "version" and how this translates into user services<br />
* Representing both history and version in the user interface<br />
<br />
4. Joe's role with the project (should he choose to have one!)<br />
<br />
5.</div>208.31.47.161http://wiki.metadataregistry.org/F2F_Meeting,_4/28/06,_SeattleF2F Meeting, 4/28/06, Seattle2006-04-10T17:20:14Z<p>208.31.47.161: </p>
<hr />
<div>== Registry Project Meeting, Seattle, 4/28/06==<br />
<br />
1. Review of current work and progress<br />
* Infrastructure, interfaces, data, testing<br />
* Plans for demo to DC UB<br />
<br />
2. Open questions and issues:<br />
<br />
* How do we deal with the Super Properties? For instance, do we allow people to add things labelled as "Notes" or do we require them to choose among the subproperties (definition, changeNote, etc.)<br />
* Is historyNote a good place to put term sources, such as we've defined in the NSDL Learning Resource Type vocabulary? We're thinking that the use of skos:inScheme should wait until we do term mapping.<br />
* In the NSDL vocabularies, we've listed the sources of definitions but there's no place to put those in skos. We're thinking it might be a something we should propose?<br />
<br />
3. Joe's role with the project (should he choose to have one!)<br />
<br />
4.</div>208.31.47.161http://wiki.metadataregistry.org/Apr._5,_2006Apr. 5, 20062006-04-03T16:24:47Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda and Notes, April 5, 2006==<br />
<br />
1. UIUC contract<br />
<br />
2. Registry screenshots (Jon will distribute prior to the meeting)<br />
<br />
3. New version document (Stuart has distributed)<br />
<br />
4. Registry demo at UB meeting<br />
* What should it include?<br />
* Is live important?<br />
* How important will it be to demonstrate versioning?</div>208.31.47.161http://wiki.metadataregistry.org/Revised_Tasks_%26_MilestonesRevised Tasks & Milestones2006-02-13T19:10:06Z<p>208.31.47.161: </p>
<hr />
<div>=Draft Revised Tasks and Milestones=<br />
<br />
<b>MILESTONES:</b><br />
<br />
Year 1:<br />
<br />
''Jan. 31''<br />
#Determine database technology and development language (Jon)<br />
#Implement main storage databases for MMS and Registry (Jon)<br />
<br />
''Feb. 28''<br />
<br />
#Implement User/Agent registration (Jon) [[Task Detail]]<br />
#Implement Vocabulary description registration (Jon)<br />
#Set up workflow to associate vocabulary descriptions and schemes (Jon & Diane)<br />
<br />
<br />
''Mar. 30''<br />
#Build interface prototypes (search, browse, display) and develop initial feedback loop on prototypes (Jon)<br />
#Determine needs for SKOS information in an editing interface (Diane & Stuart)<br />
#Define validation steps (Diane & Stuart)<br />
#Build interface prototypes (create, update) and develop initial feedback loop on prototypes (Jon)<br />
#Implement creation/updating of terms (Jon)<br />
<br />
''Apr. 30''<br />
#[Begin to involve Betatest Partners]<br />
#Define notification workflow, text, rules, including pending action notification (Diane & Jon)<br />
#Define complete Registry Administrator functionality (Diane & Jon)<br />
<br />
''July 30''<br />
#Implement and test notification (Diane & Jon)<br />
#Define schema registration workflow/data requirements (Stuart & Diane)<br />
#Build Registry administrator interface prototypes (Jon)<br />
<br />
''Aug. 30''<br />
#Build interface prototype (create, update) for schemas and develop initial feedback loop (Jon)<br />
<br />
Year 2:<br />
<br />
''Oct. 2006'' (+12): <br />
#Build interface prototype (create, update) for application profiles and develop initial feedback loop (Jon)<br />
#Develop flash movie/screencast for building APs (Diane & Jon)<br />
<br />
''Nov. 2006''<br />
#Develop requirements for community gathering around vocabularies (Jon, Diane & Stuart)<br />
<br />
<br />
'''Annual Meeting, Nov. 2006''' (+13 mos.): Demonstrable system:<br />
#End user search and display<br />
#Creation of hosted vocabularies within system<br />
#Registration of simple schema<br />
#Flash movie/screencast for building AP</div>208.31.47.161http://wiki.metadataregistry.org/Feb._10,_2006Feb. 10, 20062006-02-10T20:09:45Z<p>208.31.47.161: /* GEM Metadata Management Needs */</p>
<hr />
<div>== Agenda and Notes, 2/10/06 ==<br />
<br />
1. Discussed UIUC/IMLS project. <br />
* The problems with harvesting from UIUC: only Simple DC, no explicit connection between collections and items.<br />
* Diane will mess around with the data we have, and show Stuart and Diny how it looks and what we can do with it, including samples of CUL Metadata Services reports.<br />
* We should come up with questions for the UIUC crowd about what they'd be willing to do to help<br />
<br />
== GEM Metadata Management Needs ==<br />
<br />
2. Discuss current state of GEM metadata feeds (see below)<br />
<br />
* GEM as hybrid (fairly tight federation of data providers (current consortium) ''and'' select open harvest (''new'')<br />
* Current feed integration underway of major federation collections using GEM XML 2.0 schema (alternative collection holder or GEMCat4 RDF/XML)<br />
** Federated data--minimal quality control and minimal initial augmentation<br />
** Harvested data--potentially high quality issues and initial augmentation<br />
* Current state of collection<br />
** Approximately 45,000 consortium member conformant GEM records<br />
** Approximately 5,000 non-consortium member OAI-harvested records<br />
** Two GEM schema ''versions''--GEM 1.0 and GEM 2.0: difference is that 1.0 is pre-DC-refinements, so has lots of GEM refinements; 2.0 is much more conformant with DC, after DC instituted refinements<br />
** Variety of source encodings (OAI (minimal), GEM Syntax 0 (delimited ascii file), GEM DB-XML (first internal use of XML), GEM XML 2.0 (conformant with DCMI XML guidelines), RDF/XML (2.0))<br />
*** Current integration underway (GEM XML 2.0 Schema)<br />
** Largest proportion (over 50%) of records in top 10 collections--attack first<br />
** Largest percentage of records (26,000) coming through GEM harvest of separate (non embedded) metadata records<br />
*** While I am not yet certain of this fact, I think GEM actually controls the vast majority of these records (i.e., we harvest from ourself :-))<br />
** Only about 3,500 records harvested from resource-embedded metadata (HTML header)<br />
** Approximately<br />
<br />
3. Discuss MMS integration (per Diane/Jon emails)</div>208.31.47.161http://wiki.metadataregistry.org/Feb._10,_2006Feb. 10, 20062006-02-10T19:30:18Z<p>208.31.47.161: /* GEM Metadata Management Needs */</p>
<hr />
<div>== Agenda and Notes, 2/10/06 ==<br />
<br />
1. Discussed UIUC/IMLS project. <br />
* The problems with harvesting from UIUC: only Simple DC, no explicit connection between collections and items.<br />
* Diane will mess around with the data we have, and show Stuart and Diny how it looks and what we can do with it, including samples of CUL Metadata Services reports.<br />
* We should come up with questions for the UIUC crowd about what they'd be willing to do to help<br />
<br />
== GEM Metadata Management Needs ==<br />
<br />
2. Discuss current state of GEM metadata feeds (see below)<br />
<br />
* GEM as hybrid (fairly tight federation of data providers (current consortium) ''and'' select open harvest (''new'')<br />
* Current feed integration underway of major federation collections using GEM XML 2.0 schema (alternative collection holder or GEMCat4 RDF/XML)<br />
** Federated data--minimal quality control and minimal initial augmentation<br />
** Harvested data--potentially high quality issues and initial augmentation<br />
* Current state of collection<br />
** Approximately 45,000 consortium member conformant GEM records<br />
** Approximately 5,000 non-consortium member OAI-harvested records<br />
** Two GEM schema ''versions''--GEM 1.0 and GEM 2.0<br />
** Variety of source encodings (OAI (minimal), GEM Syntax 0, GEM DB-XML, GEM XML 2.0, RDF/XML (2.0))<br />
*** Current integration underway (GEM XML 2.0 Schema)<br />
** Largest proportion (over 50%) of records in top 10 collections--attack first<br />
** Largest percentage of records (26,000) coming through GEM harvest of separate (non embedded) metadata records<br />
*** While I am not yet certain of this fact, I think GEM actually controls the vast majority of these records (i.e., we harvest from ourself :-))<br />
** Only about 3,500 records harvested from resource-embedded metadata (HTML header)<br />
** Approximately<br />
<br />
3. Discuss MMS integration (per Diane/Jon emails)</div>208.31.47.161http://wiki.metadataregistry.org/Feb._10,_2006Feb. 10, 20062006-02-10T19:29:56Z<p>208.31.47.161: /* Agenda and Notes, 2/10/06 */</p>
<hr />
<div>== Agenda and Notes, 2/10/06 ==<br />
<br />
1. Discussed UIUC/IMLS project. <br />
* The problems with harvesting from UIUC: only Simple DC, no explicit connection between collections and items.<br />
* Diane will mess around with the data we have, and show Stuart and Diny how it looks and what we can do with it, including samples of CUL Metadata Services reports.<br />
* We should come up with questions for the UIUC crowd about what they'd be willing to do to help<br />
<br />
== GEM Metadata Management Needs ==<br />
* GEM as hybrid (fairly tight federation of data providers (current consortium) ''and'' select open harvest (''new'')<br />
* Current feed integration underway of major federation collections using GEM XML 2.0 schema (alternative collection holder or GEMCat4 RDF/XML)<br />
** Federated data--minimal quality control and minimal initial augmentation<br />
** Harvested data--potentially high quality issues and initial augmentation<br />
* Current state of collection<br />
** Approximately 45,000 consortium member conformant GEM records<br />
** Approximately 5,000 non-consortium member OAI-harvested records<br />
** Two GEM schema ''versions''--GEM 1.0 and GEM 2.0<br />
** Variety of source encodings (OAI (minimal), GEM Syntax 0, GEM DB-XML, GEM XML 2.0, RDF/XML (2.0))<br />
*** Current integration underway (GEM XML 2.0 Schema)<br />
** Largest proportion (over 50%) of records in top 10 collections--attack first<br />
** Largest percentage of records (26,000) coming through GEM harvest of separate (non embedded) metadata records<br />
*** While I am not yet certain of this fact, I think GEM actually controls the vast majority of these records (i.e., we harvest from ourself :-))<br />
** Only about 3,500 records harvested from resource-embedded metadata (HTML header)<br />
** Approximately<br />
<br />
3. Discuss MMS integration (per Diane/Jon emails)</div>208.31.47.161http://wiki.metadataregistry.org/Feb._10,_2006Feb. 10, 20062006-02-10T19:29:23Z<p>208.31.47.161: </p>
<hr />
<div>== Agenda and Notes, 2/10/06 ==<br />
<br />
1. Discussed UIUC/IMLS project. <br />
* The problems with harvesting from UIUC: only Simple DC, no explicit connection between collections and items.<br />
* Diane will mess around with the data we have, and show Stuart and Diny how it looks and what we can do with it, including samples of CUL Metadata Services reports.<br />
* We should come up with questions for the UIUC crowd about what they'd be willing to do to help<br />
<br />
2. Discuss current state of GEM metadata feeds (see below)<br />
<br />
== GEM Metadata Management Needs ==<br />
* GEM as hybrid (fairly tight federation of data providers (current consortium) ''and'' select open harvest (''new'')<br />
* Current feed integration underway of major federation collections using GEM XML 2.0 schema (alternative collection holder or GEMCat4 RDF/XML)<br />
** Federated data--minimal quality control and minimal initial augmentation<br />
** Harvested data--potentially high quality issues and initial augmentation<br />
* Current state of collection<br />
** Approximately 45,000 consortium member conformant GEM records<br />
** Approximately 5,000 non-consortium member OAI-harvested records<br />
** Two GEM schema ''versions''--GEM 1.0 and GEM 2.0<br />
** Variety of source encodings (OAI (minimal), GEM Syntax 0, GEM DB-XML, GEM XML 2.0, RDF/XML (2.0))<br />
*** Current integration underway (GEM XML 2.0 Schema)<br />
** Largest proportion (over 50%) of records in top 10 collections--attack first<br />
** Largest percentage of records (26,000) coming through GEM harvest of separate (non embedded) metadata records<br />
*** While I am not yet certain of this fact, I think GEM actually controls the vast majority of these records (i.e., we harvest from ourself :-))<br />
** Only about 3,500 records harvested from resource-embedded metadata (HTML header)<br />
** Approximately<br />
<br />
3. Discuss MMS integration (per Diane/Jon emails)</div>208.31.47.161http://wiki.metadataregistry.org/Feb._8,_2006Feb. 8, 20062006-02-08T21:00:31Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda and Notes, Feb. 10, 2006 (date change)==<br />
<br />
1. Jon added a more detailed [http://phoenix.ischool.washington.edu/wiki/index.php/Task_Detail Task List], linked from the [http://phoenix.ischool.washington.edu/wiki/index.php/Revised_Tasks_%26_Milestones Revised Tasks & Milestons] page<br />
<br />
2. Progress on the IMLS data evaluation (Diane)<br />
<br />
3. Diane and Jon's braindump on rebuilding the GEM Provider Network</div>208.31.47.161http://wiki.metadataregistry.org/Feb._1,_2006Feb. 1, 20062006-02-01T19:40:07Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda and Notes, Telecon, Feb. 1, 2006==<br />
<br />
1. Are we using purl.org or purl.oclc.org? Both appear in the SKOS representations that Oknam did.<br />
<br />
Stuart will ask Oknam to change them all to purl.org, even though there doesn't seem to be a substantive difference. <br />
<br />
2. Report from Jon. <br />
<br />
He's working on a task list based on starting user registration for both the Registry and the MMS and having something to show at the end of the month.<br />
<br />
3. Discussion of the data needed for the UIUC reports. Diane will have some files for Diny and Stuart to look like at WebWise, so we can figure out what the evaluations should look like. Diane will look at some of the old NSDL evaluations from Cornell Metadata Services. Stuart will look for their collection data and from where their search portal is, because he thinks he saw audience data in a search. We'd like to have enough information to ask questions of the UIUC folks before WebWise if possible.</div>208.31.47.161http://wiki.metadataregistry.org/Feb._1,_2006Feb. 1, 20062006-02-01T18:02:36Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda and Notes, Telecon, Feb. 1, 2006==<br />
<br />
1. Are we using purl.org or purl.oclc.org? Both appear in the SKOS representations that Oknam did.<br />
<br />
2. Report from Jon.</div>208.31.47.161http://wiki.metadataregistry.org/Feb._1,_2006Feb. 1, 20062006-01-26T16:33:40Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda and Notes, Telecon, Feb. 1, 2006==<br />
<br />
1. Are we using purl.org or purl.oclc.org? Both appear in the SKOS representations that Oknam did.</div>208.31.47.161http://wiki.metadataregistry.org/Teleconference_Agendas_and_NotesTeleconference Agendas and Notes2006-01-26T16:32:41Z<p>208.31.47.161: </p>
<hr />
<div>=== Teleconference Agendas and Notes ===<br />
<br />
Teleconferences are scheduled for Wednesday afternoons, 2:00 (Eastern)/11:00 (Pacific). Calls will be initiated from Seattle.<br />
<br />
<ul><br />
<li>[[Feb. 22, 2006]]<br />
<li>[[Feb. 15, 2006]]<br />
<li>[[Feb. 8, 2006]]<br />
<li>[[Feb. 1, 2006]]<br />
<li>[[Jan. 25, 2006]]<br />
<li>[[Jan. 18, 2006]]<br />
<li>[[Jan. 11, 2006]] Cancelled<br />
<li>[[Jan. 4, 2006]]<br />
<li>[[Dec. 21, 2005]]<br />
<li>[[Dec. 14, 2005]] Cancelled<br />
<li>[[Dec. 7, 2005]]<br />
<li>[[Dec. 1, 2005]]<br />
<li>[[Oct. 26, 2005]]<br />
<li>[[Oct. 19, 2005]] Cancelled<br />
<li>[[Oct. 12, 2005]]<br />
<li>[[Oct. 5, 2005]]<br />
<li>[[Oct. 3, 2005]]<br />
<li>[[Sept. 30, 2005]]<br />
<li>[[Sept. 21, 2005]]<br />
<li> Sept. 7 and 14th will be skipped (DC2005 and vacations)<br />
<li>[[Aug. 31, 2005]] (Stuart will be absent)<br />
<li>[[Aug. 24, 2005]] <br />
<li>[[Aug. 17, 2005]] (Jon will be absent)<br />
<li>[[Aug. 10, 2005]] <br />
</ul></div>208.31.47.161http://wiki.metadataregistry.org/Revised_Tasks_%26_MilestonesRevised Tasks & Milestones2006-01-26T16:07:16Z<p>208.31.47.161: </p>
<hr />
<div>=Draft Revised Tasks and Milestones=<br />
<br />
<b>MILESTONES:</b><br />
<br />
Year 1:<br />
<br />
''Jan. 31''<br />
#Determine database technology and development language (Jon)<br />
#Implement main storage databases for MMS and Registry (Jon)<br />
<br />
''Feb. 28''<br />
<br />
#Implement User/Agent registration (Jon)<br />
#Implement Vocabulary description registration (Jon)<br />
#Set up workflow to associate vocabulary descriptions and schemes (Jon & Diane)<br />
<br />
<br />
''Mar. 30''<br />
#Build interface prototypes (search, browse, display) and develop initial feedback loop on prototypes (Jon)<br />
#Determine needs for SKOS information (Diane & Stuart)<br />
#Define validation steps (Diane & Stuart)<br />
#Build interface prototypes (create, update) and develop initial feedback loop on prototypes (Jon)<br />
#Implement creation/updating of terms (Jon)<br />
<br />
''Apr. 30''<br />
#[Begin to involve Betatest Partners]<br />
#Define notification workflow, text, rules, including pending action notification (Diane & Jon)<br />
#Define complete Registry Administrator functionality (Diane & Jon)<br />
<br />
''July 30''<br />
#Implement and test notification (Diane & Jon)<br />
#Define schema registration workflow/data requirements (Stuart & Diane)<br />
#Build Registry administrator interface prototypes (Jon)<br />
<br />
''Aug. 30''<br />
#Build interface prototype (create, update) for schemas and develop initial feedback loop (Jon)<br />
<br />
Year 2:<br />
<br />
''Oct. 2006'' (+12): <br />
#Build interface prototype (create, update) for application profiles and develop initial feedback loop (Jon)<br />
#Develop flash movie/screencast for building APs (Diane & Jon)<br />
<br />
''Nov. 2006''<br />
#Develop requirements for community gathering around vocabularies (Jon, Diane & Stuart)<br />
<br />
<br />
'''Annual Meeting, Nov. 2006''' (+13 mos.): Demonstrable system:<br />
#End user search and display<br />
#Creation of hosted vocabularies within system<br />
#Registration of simple schema<br />
#Flash movie/screencast for building AP</div>208.31.47.161http://wiki.metadataregistry.org/Jan._25,_2006Jan. 25, 20062006-01-25T19:17:52Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda and Notes, telecon of Jan. 25, 2006==<br />
<br />
1. Report from Jon on progress and next steps<br />
#* Jon and Diane will be working on getting something specified and "out" for viewing in about 5 weeks.<br />
<br />
2. Discussion on Jenn Riley's response and how we want to proceed. <br />
#* We will continue to converse with her about these issues in hopes that they might be willing to help us define and test services</div>208.31.47.161http://wiki.metadataregistry.org/Jan._25,_2006Jan. 25, 20062006-01-25T16:34:05Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda and Notes, telecon of Jan. 25, 2006==<br />
<br />
1. Report from Jon on progress and next steps<br />
<br />
2. Discussion on Jenn Riley's response and how we want to proceed</div>208.31.47.161http://wiki.metadataregistry.org/Jan._18,_2006Jan. 18, 20062006-01-18T20:03:29Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda & Notes, Jan. 18, 2006==<br />
<br />
1. Report from Jon on technology exploration.<br />
http://phoenix.ischool.washington.edu/wiki/index.php/Implementing_Technologies<br />
<br />
* Jon discussed his process and conclusions in determining the best options for building the Registry and MMS. <br />
<br />
2. Preliminary steps for harvesting data for Spotfire Analysis<br />
http://phoenix.ischool.washington.edu/wiki/index.php/HarvestSteps<br />
<br />
* Jon explained the reasoning behind this piece of the process based on what had been available for NSDL. <br />
* Diane, Diny and Stuart will be at the WebWise conference and we will meet--Diane will bring the PC laptop to demonstrate SpotFire.<br />
* Stuart mentioned a possible project with the Dewey folks, Diane will send him a link to the MARC Classification Format<br />
<br />
3. Beginning to think about a registry paper for DC2006. Diane has drafted an [http://phoenix.ischool.washington.edu/wiki/index.php/Draft_Outline:_DC2006_paper outline].<br />
<br />
* Stuart will be doing an ASN paper for DC2006, but will work with Jon and Diane on the registry paper as well.</div>208.31.47.161http://wiki.metadataregistry.org/HarvestStepsHarvestSteps2006-01-18T19:09:36Z<p>208.31.47.161: /* Harvest steps for tab-delimted files for Spotfire Data analysis: */</p>
<hr />
<div>== Harvest steps for tab-delimited files for Spotfire Data analysis: ==<br />
=== harvest to files ===<br />
note: file for each resumption block<br />
note: filename should be [service_id]_[set_id]_[metadata-prefix]_[yyyy-mm-dd-hh-mm-ss(request time)_[00000(chunk number)].xml<br />
*store harvest log for each harvest with<br />
**stat section<br />
***harvest stat<br />
****start time<br />
****end time<br />
****record count<br />
****http errors<br />
****http redirects<br />
***chunk stats (written at the top of each chunk file?)<br />
****chunk 01<br />
*****start time<br />
*****end time<br />
*****record count<br />
=== parse the files to create csv ===<br />
*get total record count from harvest stats -- x and number of files -- z<br />
*get number of requested records from csv convert command args -- y<br />
*divide y/z and get that number of random records from each file<br />
*get them all if y == 0<br />
*open csv file for write<br>note: filename should be [service_id]_[set_id]_[yyyy-mm-dd-hh-mm-ss(request time).csv<br />
*for each record<br />
**store record.header.identifier<br />
**store namespaces -- record.metadata.dc xmlns:dc, xmlns:oai_dc,xmlns:xsi<br />
**for each row in record<br />
***metadata record id == record.header.identifier (stored)<br />
***element namespace == record.metadata.dc xmlns:dc, xmlns:oai_dc,xmlns:xsi (stored)<br />
***element name == record.metadata.dc.[any element]<br />
***element value == record.metadata.dc.[any element].value<br />
***element type == record.metadata.dc.[any element].type.value<br />
***element lang == record.metadata.dc.[any element].lang.value</div>208.31.47.161http://wiki.metadataregistry.org/Jan._18,_2006Jan. 18, 20062006-01-18T18:30:01Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda & Notes, Jan. 18, 2006==<br />
<br />
1. Report from Jon on technology exploration.<br />
<br />
2. Beginning to think about a registry paper for DC2006. Diane has drafted an [http://phoenix.ischool.washington.edu/wiki/index.php/Draft_Outline:_DC2006_paper outline].</div>208.31.47.161http://wiki.metadataregistry.org/Draft_Outline:_DC2006_paperDraft Outline: DC2006 paper2006-01-18T18:28:49Z<p>208.31.47.161: </p>
<hr />
<div>==Building a Registry for Controlled Vocabularies: Draft Outline==<br />
<br />
- [ ] What kind of Registry are we building?<br />
- [ ] Starting at the controlled vocabulary end<br />
- [ ] Focusing on full registry services<br />
- [ ] Contribution by batch or individual input<br />
- [ ] Full range of output mechanisms<br />
- [ ] What are the challenges?<br />
- [ ] Versioning: Vocabulary level and term level<br />
- [ ] Making the registry an integral part of the document/publish<br />
strategy for vocabulary managers (not just another task with<br />
no payback)<br />
- [ ] Building user interfaces that can be used by all levels of<br />
users, not just experts<br />
- [ ] Accepting batch input in many different formats<br />
- [ ] Building the 'distribution' pieces in distributed registry<br />
dream<br />
- [ ] Is SKOS sifficient for these tasks?<br />
- [ ] Local extensions needed for admin data that must be output<br />
(status)<br />
- [ ] Ref. Joe Tennis' paper about maintenance<br />
- [ ] How will what we learn building this end of the registry inform<br />
the other parts?</div>208.31.47.161http://wiki.metadataregistry.org/NSDL_RegistryNSDL Registry2006-01-18T18:27:40Z<p>208.31.47.161: /* An NSDL Registry: Supporting Interoperable Metadata Distribution */</p>
<hr />
<div>=== An NSDL Registry: Supporting Interoperable Metadata Distribution ===<br />
<br />
What we're about: <i>Building on work in the Dublin Core community on metadata registries, we propose to develop and deploy an NSDL metadata registry (hereafter, ‘the Registry’) to enable collection holders creating metadata for their collections and various applications that generate, consume and process metadata to identify, declare and publish their metadata schemas (element/property sets) and schemes (value spaces/controlled vocabularies) in support of discovery, reuse, standardization and interoperability within NSDL and globally. We proposed to accomplish this task by building on existing work within the communities focused on metadata management issues including the Dublin Core Metadata Initiative (DCMI), the World Wide Web Consortium (W3C), and researchers in networked knowledge organization systems. In particular, we intend to seed development of the Registry with the DCMI Registry open source application. </i><br />
----<br />
[[Timeline of Work]]<br />
----<br />
<br />
[[Working Notes and Documentation]]<br />
<br />
[[Tasks and Milestones]]<br />
<br />
[[Revised Tasks & Milestones]]<br />
<br />
----<br />
<br />
[[Teleconference Agendas and Notes]]<br />
<br />
[[Other Meetings and Notes]]<br />
<br />
[[Draft Outline: DC2006 paper]]<br />
<br />
----<br />
<br />
Links:<br />
<br />
----<br />
<br />
Public Pages:<br />
*[http://registry.comm.nsdl.org/cgi-bin/wiki.pl?NSDL_Registry Public Wiki]<br />
*[http://eg2.ischool.washington.edu/registry Registry Web Site]</div>208.31.47.161http://wiki.metadataregistry.org/General_Use_Case_InformationGeneral Use Case Information2006-01-18T15:26:13Z<p>208.31.47.161: /* Vocabulary and Member Term States (Statuses?) */</p>
<hr />
<div>=Actors=<br />
==Human Actors==<br />
;System Administrator:Overall system administrator. Responsible for system-level software and hardware maintenance<br />
;Registry Manager:Person (or persons) responsible for the administrative tasks involved in the management of a registry<br />
;Vocabulary Editor/Reviewer: Person (or persons) responsible for editorial functions related to submitted vocabularies <br />
;Visitor:Anyone viewing or browsing the site who is not logged in, including registered Maintainers who have not yet logged in.<br />
;Registered User: A Visitor who has registered himself/herself for the purpose of registering an organization or vocabulary. A Registered User may assume an additional role (Maintainer, Organization Contact) while registering an organization or vocabulary.<br />
;Organization Contact: Person acting on behalf of an organization, to whom notifications to the Organization may be sent.<br />
;Maintainer:Person responsible for maintaining a vocabulary<br />
<br />
==Non-human Actors==<br />
;Registry:The registry software, including user interfaces, processing systems, and services<br />
;Service:An interface intended to be used by machines that provides data in response to a request<br />
;Service Consumer:Machine requesting data from a service<br />
;Organization:Basically a term for for group of persons or an educational or business unit rather than an individual. For instance, an NSDL Project is an organization. In the current context the organization is also the entity responsible for the vocabulary. Vocabularies are associated with an Organization and maintained by a Maintainer who is authorized by the Organization. (Policy question?)<br />
<br />
=Terms=<br />
;Vocabulary:[Merriam-Webster] "a list or collection of words or of words and phrases usually alphabetically arranged and explained or defined" ; [In the context of this project] "A set of concepts, represented by words and word relationships, presented in a structured manner." [NOTE: the [http://dublincore.org/documents/abstract-model/ DC Abstract Model] uses the term <i>Vocabulary Encoding Scheme</i>, defined as "A vocabulary encoding scheme is a class that indicates that the value of a property is taken from a controlled vocabulary (or concept-space), such as the Library of Congress Subject Headings"]<br />
;Hosted Vocabulary: A vocabulary whose canonical (official) version resides, or is "hosted" in the Registry. <br />
;Non-hosted Vocabulary: A vocabulary that is published (exposed) through the Registry but that is created and maintained by its promulgating agency in a separate registry or as a Web-addressable file in its own namespace. <br />
;Terms:[http://dublincore.org/documents/abstract-model/ DC Abstract Model] "The generic name for a property (i.e. element or element refinement), vocabulary encoding scheme, syntax encoding scheme or concept taken from a controlled vocabulary (concept space)"<br />
;Tokens:[from Wikipedia] "In computer science, specifically lexical analysis, a token is usually a word or an atomic element within a string. Tokenizing is systematically replacing portions of a string by such corresponding token"<br />
;Simple Knowledge Organization System (SKOS):[from [http://www.w3.org/2004/02/skos/ SKOS Home Page]] "SKOS is an area of work developing specifications and standards to support the use of knowledge organization systems (KOS) such as thesauri, classification schemes, subject heading lists, taxonomies, terminologies, glossaries and other types of controlled vocabulary within the framework of the semantic web"<br />
;PURLs:[from the [http://purl.org/ OCLC PURL Home page]] "A PURL is a Persistent Uniform Resource Locator. Functionally, a PURL is a URL. However, instead of pointing directly to the location of an Internet resource, a PURL points to an intermediate resolution service. The PURL resolution service associates the PURL with the actual URL and returns that URL to the client. The client can then complete the URL transaction in the normal fashion. In Web parlance, this is a standard HTTP redirect"<br />
<br />
=Vocabulary and Member Term States (Statuses?)=<br />
;Draft:The state of a schema (element set or member property) or a scheme (vocabulary and or member vocabulary term) that has been created in the registry by a Maintainer but that has not been submitted to the Registry Manager (or delegate)<br />
;Submitted:The state of a schema (element set) or a scheme (vocabulary and vocabulary terms) that has been submitted by a Maintainer and is under review by the Registry Manager (or delegate)<br />
;Published:The state of a schema (element set or member properties) or a scheme (vocabulary and member vocabulary terms) that has been exposed to external human and machine agents through the registry<br />
;Deprecated:The state of a schema (i.e., element set or member property) or a scheme (i.e., vocabulary or member vocabulary term) the use of which is no longer advised, most often because it has been withdrawn or replaced. Deprecation is used to indicate that a particular schema (i.e., element set or member property) or scheme (i.e., vocabulary or member vocabulary term) is preserved for purposes of backward-compatibility, but should be phased out in the creation of future instance metadata. Deprecated schemas and schemes are ''never'' deleted.<br />
<br />
=Policies=<br />
WARNING - assumption alert!! Many of the use cases below make assumptions about yet-to-be-decided policies (as of 9/2005)<br />
*Schemas and schemes must be associated with an Organization that acts as the Entity responsible for the Vocabulary<br />
*Maintainers are individuals and they must be associated with an Organization in order to maintain an Organization's schemas and schemes<br />
*A Maintainer may be associated with more than one Organization and more than one schemas and schemes<br />
*Organization Contacts specifically authorize individual Maintainers to maintain a specific scheme or schema. Reasonable measures will be taken to assure the Registry and Registered Organizations against fraud and error. The workflow that seeks to ensure this is as follows: (1) user registers as the Organization Contact for schemas and schemes, (2) Organization Contact creates Organization record; (3) Organization Contact elects to perform the role of Maintainer or to register Maintainers. Once registered as a Maintainer, a person may serve the role of maintainer for more than one Organization. <br />
*Organizations must be able to be associated with an internet domain that will form the root of individual Vocabulary namespaces, or agree to allow the registry domain to substitute.</div>208.31.47.161http://wiki.metadataregistry.org/Teleconference_Agendas_and_NotesTeleconference Agendas and Notes2006-01-17T15:55:37Z<p>208.31.47.161: /* Teleconference Agendas and Notes */</p>
<hr />
<div>=== Teleconference Agendas and Notes ===<br />
<br />
Teleconferences are scheduled for Wednesday afternoons, 2:00 (Eastern)/11:00 (Pacific). Calls will be initiated from Seattle.<br />
<br />
<ul><br />
<li>[[Jan. 25, 2006]]<br />
<li>[[Jan. 18, 2006]]<br />
<li>[[Jan. 11, 2006]] Cancelled<br />
<li>[[Jan. 4, 2006]]<br />
<li>[[Dec. 21, 2005]]<br />
<li>[[Dec. 14, 2005]] Cancelled<br />
<li>[[Dec. 7, 2005]]<br />
<li>[[Dec. 1, 2005]]<br />
<li>[[Oct. 26, 2005]]<br />
<li>[[Oct. 19, 2005]] Cancelled<br />
<li>[[Oct. 12, 2005]]<br />
<li>[[Oct. 5, 2005]]<br />
<li>[[Oct. 3, 2005]]<br />
<li>[[Sept. 30, 2005]]<br />
<li>[[Sept. 21, 2005]]<br />
<li> Sept. 7 and 14th will be skipped (DC2005 and vacations)<br />
<li>[[Aug. 31, 2005]] (Stuart will be absent)<br />
<li>[[Aug. 24, 2005]] <br />
<li>[[Aug. 17, 2005]] (Jon will be absent)<br />
<li>[[Aug. 10, 2005]] <br />
</ul></div>208.31.47.161http://wiki.metadataregistry.org/Jan._18,_2006Jan. 18, 20062006-01-17T15:55:06Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda & Notes, Jan. 18, 2006==<br />
<br />
1. Report from Jon on technology exploration.<br />
<br />
2. Beginning to think about a registry paper for DC2006. Diane will distribute a proposed outline.</div>208.31.47.161http://wiki.metadataregistry.org/Jan._4,_2006Jan. 4, 20062006-01-04T19:59:54Z<p>208.31.47.161: </p>
<hr />
<div>==Telecon Agenda and Notes, Jan. 4, 2006==<br />
<br />
1. Research server acquisition & networking (Cornell)<br />
* Diane will contact Roberta at OSP about the new proposal and the movement of money from the computer services line to supplies on the NSF Registry grant, so that we can buy a server for Jon<br />
* Diane will also confirm the percentage of indirects that Cornell will require on the second proposal, and whether it's different if Cornell leads or not<br />
2. Review of revised Milestones (see: http://phoenix.ischool.washington.edu/wiki/index.php/Revised_Tasks_%26_Milestones)<br />
* Changes were primarily to move some deliverable dates further out and to align with the MMS development<br />
3. Review of "Commonalities" spreadsheet (sent via email)<br />
* A few new things were added and the spreadsheet will be redistributed</div>208.31.47.161http://wiki.metadataregistry.org/Jan._4,_2006Jan. 4, 20062006-01-04T19:59:14Z<p>208.31.47.161: </p>
<hr />
<div>==Telecon Agenda and Notes, Jan. 4, 2006==<br />
<br />
1. Research server acquisition & networking (Cornell)<br />
* Diane will contact Roberta at OSP about the new proposal and the movement of money from the computer services line to supplies on the NSF Registry grant, so that we can buy a server for Jon<br />
* Diane will also confirm the percentage of indirects that Cornell will require on the second proposal, and whether it's different if Cornell leads or not<br />
2. Review of revised Milestones (see: http://phoenix.ischool.washington.edu/wiki/index.php/Revised_Tasks_%26_Milestones)<br />
* Changes were primarily to move some deliverable dates further out and to align with the MMS development<br />
3. Review of "Commonalities" spreadsheet (sent via email)<br />
* A few new things were added and the spreadsheet will be added to the docs list</div>208.31.47.161http://wiki.metadataregistry.org/Jan._4,_2006Jan. 4, 20062006-01-04T19:07:49Z<p>208.31.47.161: </p>
<hr />
<div>==Telecon Agenda and Notes, Jan. 4, 2006==<br />
<br />
#Research server acquisition & networking (Cornell)<br />
* Diane will contact Roberta at OSP about the new proposal and the movement of money from the computer services line to supplies on the NSF Registry grant, so that we can buy a server for Jon<br />
* <br />
#Review of revised Milestones (see: http://phoenix.ischool.washington.edu/wiki/index.php/Revised_Tasks_%26_Milestones)<br />
#Review of "Commonalities" spreadsheet (sent via email)</div>208.31.47.161http://wiki.metadataregistry.org/Jan._4,_2006Jan. 4, 20062006-01-04T18:28:07Z<p>208.31.47.161: </p>
<hr />
<div>==Telecon Agenda and Notes, Jan. 4, 2006==<br />
<br />
#Review of revised Milestones (see: http://phoenix.ischool.washington.edu/wiki/index.php/Revised_Tasks_%26_Milestones)<br />
#Review of "Commonalities" spreadsheet (sent via email)</div>208.31.47.161http://wiki.metadataregistry.org/Jan._4,_2006Jan. 4, 20062006-01-04T15:32:26Z<p>208.31.47.161: </p>
<hr />
<div>==Telecon Agenda and Notes, Jan. 4, 2006==<br />
<br />
#Review of revised Milestones (see: http://phoenix.ischool.washington.edu/wiki/index.php/Revised_Tasks_%26_Milestones)<br />
#Report from Jon</div>208.31.47.161http://wiki.metadataregistry.org/Jan._4,_2006Jan. 4, 20062006-01-04T15:29:50Z<p>208.31.47.161: </p>
<hr />
<div>==Telecon Agenda and Notes, Jan. 4, 2006==<br />
<br />
#Review of revised Milestones<br />
#Report from Jon</div>208.31.47.161http://wiki.metadataregistry.org/Re-implementing_the_MMSRe-implementing the MMS2005-12-31T16:49:47Z<p>208.31.47.161: /* Phase I */</p>
<hr />
<div>=Re-Implementing the MMS for GEM=<br />
<br />
==Phase I==<br />
<br />
Current implementation has very tight ties to an Oracle database. For new, generalized MMS, the functions need to be more abstract, in order to work with any database. The internal user management systems were handed off to an external service in the original implementation. In the re-implementation, roles and rights for users need to be abstracted to work either wholly within the MMS or linked to an external user authentication system.<br />
<br />
#New implementation of the main Repository database (JP estimate: 2 weeks)<br />
#* Currently based on Oracle 9i. We need to decide whether to go with Oracle's new release (10g called 'Express Edition') which is free for limited use, or switch to MySQL. Regardless of which is chosen for the first re-implementation, the code will be developed to make that decision a local one, with the MMS working with any database.<br />
#* One advantage of sticking with Oracle is that they are coming out with a native RDF database. Another advantage is that some Oracle specific development done for the NSDL can be re-used.<br />
#* Develop simple ingest process to bring data into Repository<br />
#New implementation of the internal management database (JP estimate: 3 days)<br />
#* The current database has been developed over time and is due for re-factoring, though the core ideas are the same. It is currently based on Qualified DC and it's not clear that anything else would be necessary for this portion of the internal work.<br />
#Abstracting user and service management and adding to internal management database (using registry model) (JP estimate: 4 weeks)<br />
#* User management was based on an incomplete integration with SourceForge which made it impossible to manage users effectively. Service management was limited for some of the same reasons, although internally we set up a framework that was managed manually.<br />
#* A new user management module needs to be developed that can be easily integrated into other user management systems. This will allow the building of a service management based on lessons learned in the NSDL implementation.<br />
#Setup of simple services infrastructure (similar to Recommender) (JP estimate: 2 weeks)<br />
#* Current recommender too closely integrated into the MMS management database<br />
#* New implementation will be a separate service harvested into the Repository<br />
#* Other services should be set up on the same model: harvest, change, expose. This includes human mediated services such as editing and alignment services. CWIS might be an effective start on this (though should be pre-configured).<br />
#Implement new harvester (JP estimate: 3 weeks)<br />
#* New harvester should be based on existing harvester, modified to be more forgiving of invalid XML, that will report errors down to specific line, enabling effective notification. Acceptance should cascade from full harvest to statement-by-statement, only rejecting the smallest possible portions of a potential harvest.<br />
#Re-implementing the MMS OAI server (JP estimate: 3 days)<br />
<br />
==Phase II==<br />
<br />
#Adjust the metadata editor to accommodate any metadata schema and work with the simple services structure<br />
#* Current metadata editor tightly tied to qualified Dublin Core (flat and non-hierarchical) and with the database. Needs to stand alone as a separate service.<br />
#* Enabling editing for hierarchical schemas (such as LOM) will require additional work<br />
#Implement services registry on top of existing components (user management and repository)<br />
#* Needs to make a distinction between services and service providers, which doesn't currently exist.<br />
#* Current service setup is unidirectional (only works with services it controls). Also needs to register service interfaces that can be managed by the MMS (Lenny)<br />
#* Explicit round trip services<br />
#Implement error handling and notifications<br />
#* Agents choose preferred notification type and methodology (email, RSS, etc.)<br />
#* Defaults are configured by agent role<br />
#Setup safe transformation service, generalized to any repository<br />
#* Another simple service separately configured<br />
#* Based on NSDL safe transforms<br />
#Upgrade the MMS OAI server <br />
#* Exising server needs to have data backend made more abstract to deal with any data schema or source<br />
#* Needs to be distributable for use with any system<br />
<br />
==Phase III==<br />
<br />
#Implement comprehensive harvest diagnostics, validity checkers and helpdesk functionality<br />
#* New or changed harvest generate statistical summary and sample or full export file for evaluation tool (generated on the fly)<br />
#* May use separate third party software for helpdesk<br />
#Implement distributed GEM community services (includes OAI server capable of working on many platforms, plugin data connections, etc.)<br />
#Implement collection-specific transforms<br />
<br />
==Phase IV==<br />
<br />
#Implement metadata augmentation, improvement and rating services<br />
#Non-OAI data services<br />
#Secure OAI services</div>208.31.47.161http://wiki.metadataregistry.org/Teleconference_Agendas_and_NotesTeleconference Agendas and Notes2005-12-21T19:40:24Z<p>208.31.47.161: </p>
<hr />
<div>=== Teleconference Agendas and Notes ===<br />
<br />
Teleconferences are scheduled for Wednesday afternoons, 2:00 (Eastern)/11:00 (Pacific). Calls will be initiated from Seattle.<br />
<br />
<ul><br />
<li>[[Jan. 25, 2006]]<br />
<li>[[Jan. 18, 2006]]<br />
<li>[[Jan. 11, 2006]]<br />
<li>[[Jan. 4, 2006]]<br />
<li>[[Dec. 21, 2005]]<br />
<li>[[Dec. 14, 2005]] Cancelled<br />
<li>[[Dec. 7, 2005]]<br />
<li>[[Dec. 1, 2005]]<br />
<li>[[Oct. 26, 2005]]<br />
<li>[[Oct. 19, 2005]] Cancelled<br />
<li>[[Oct. 12, 2005]]<br />
<li>[[Oct. 5, 2005]]<br />
<li>[[Oct. 3, 2005]]<br />
<li>[[Sept. 30, 2005]]<br />
<li>[[Sept. 21, 2005]]<br />
<li> Sept. 7 and 14th will be skipped (DC2005 and vacations)<br />
<li>[[Aug. 31, 2005]] (Stuart will be absent)<br />
<li>[[Aug. 24, 2005]] <br />
<li>[[Aug. 17, 2005]] (Jon will be absent)<br />
<li>[[Aug. 10, 2005]] <br />
</ul></div>208.31.47.161http://wiki.metadataregistry.org/Dec._21,_2005Dec. 21, 20052005-12-21T19:37:35Z<p>208.31.47.161: </p>
<hr />
<div>==Telecon Agenda and Notes, Dec. 21, 2005==<br />
<br />
1. Spotfire--Stuart has called and tried to talk to them about purchasing, we will get the same deal as Cornell got. He has to do it through UW purchasing, and he's trying to get it expedited. Apparently there's a UW faculty member with a Spotfire server license, and Stuart will explore whether we might be able to use some of that.<br />
<br />
2. Stuart has been working on the budget, for the moment with UW as lead. He will finish the spreadsheet today. Jon, Diane and Diny can fill in our tabs and see where we are.<br />
<br />
3. Ryan and Stuart have talked about the shift in direction. Server on UW end is being used for other things, so we need to look elsewhere for long term. The UW server is available in the short term. <br />
<br />
4. Stuart will talk to Diny about under which category our second IMLS proposal will be submitted.<br />
<br />
5. Budget that Jon submitted for servers and IP services<br />
# What budget it comes from (Cornell re-budgeted Registry)<br />
# Any other considerations<br />
<br />
6. Reworking the milestones (see: http://phoenix.ischool.washington.edu/wiki/index.php/Revised_Tasks_%26_Milestones) Diane and Jon will work through the functional requirements for both and try to reconcile the tasks and milestones coming from that.<br />
<br />
7. New doctoral student--Melanie Feinberg (10 week UW Winter Quarter)--versioning (research practicum--RDF modeling). She will work based on the assumption that we would want to output the full versioning information for a vocabulary.<br />
<br />
Next Registry call the first week in January.</div>208.31.47.161http://wiki.metadataregistry.org/Dec._21,_2005Dec. 21, 20052005-12-21T19:33:56Z<p>208.31.47.161: </p>
<hr />
<div>==Telecon Agenda and Notes, Dec. 21, 2005==<br />
<br />
* Spotfire--Stuart has called and tried to talk to them about purchasing, we will get the same deal as Cornell got. He has to do it through UW purchasing, and he's trying to get it expedited. Apparently there's a UW faculty member with a Spotfire server license, and Stuart will explore whether we might be able to use some of that.<br />
<br />
* Stuart has been working on the budget, for the moment with UW as lead. He will finish the spreadsheet today. Jon, Diane and Diny can fill in our tabs and see where we are.<br />
<br />
* Ryan and Stuart have talked about the shift in direction. Server on UW end is being used for other things, so we need to look elsewhere for long term. The UW server is available in the short term. <br />
<br />
* Stuart will talk to Diny about under which category our second IMLS proposal will be submitted.<br />
<br />
* Budget that Jon submitted for servers and IP services<br />
# What budget it comes from (Cornell re-budgeted Registry)<br />
# Any other considerations<br />
<br />
2. Reworking the milestones (see: http://phoenix.ischool.washington.edu/wiki/index.php/Revised_Tasks_%26_Milestones) Diane and Jon will work through the functional requirements for both and try to reconcile the tasks and milestones coming from that.<br />
<br />
3. New doctoral student--Melanie Feinberg (10 week UW Winter Quarter)--versioning (research practicum--RDF modeling). She will work based on the assumption that we would want to output the full versioning information for a vocabulary.<br />
<br />
Next Registry call the first week in January.</div>208.31.47.161http://wiki.metadataregistry.org/Dec._21,_2005Dec. 21, 20052005-12-21T19:29:03Z<p>208.31.47.161: </p>
<hr />
<div>==Telecon Agenda and Notes, Dec. 21, 2005==<br />
<br />
* Spotfire--Stuart has called and tried to talk to them about purchasing, we will get the same deal as Cornell got. He has to do it through UW purchasing, and he's trying to get it expedited. Apparently there's a UW faculty member with a Spotfire server license, and Stuart will explore whether we might be able to use some of that.<br />
<br />
* Stuart has been working on the budget, for the moment with UW as lead. He will finish the spreadsheet today. Jon, Diane and Diny can fill in our tabs and see where we are.<br />
<br />
* Ryan and Stuart have talked about the shift in direction. Server on UW end is being used for other things, so we need to look elsewhere for long term. The UW server is available in the short term. <br />
<br />
* Stuart will talk to Diny about which category our second IMLS proposal will be submitted.<br />
<br />
* Budget that Jon submitted for servers and IP services<br />
# What budget it comes from (Cornell re-budgeted Registry)<br />
# Any other considerations<br />
<br />
2. Reworking the milestones (see: http://phoenix.ischool.washington.edu/wiki/index.php/Revised_Tasks_%26_Milestones) Diane and Jon will work through the functional requirements for both and try to reconcile the tasks and milestones coming from that.<br />
<br />
3. New doctoral student--Melanie Feinberg (10 week UW Winter Quarter)--versioning (research practicum--RDF modeling)</div>208.31.47.161http://wiki.metadataregistry.org/Main_PageMain Page2005-12-21T19:01:09Z<p>208.31.47.161: </p>
<hr />
<div>=== Current Projects -- "The Partnership" ===<br />
<br />
At the University of Washington:<br />
* [mailto:sasutton@u.washington.edu Stuart A. Sutton]<br />
* [mailto:rjlaundr@u.washington.edu Ryan Laundry]<br />
* [mailto:feinberg@u.washington.edu Melanie D. Feinberg]<br />
* [mailto:parko.u.washington.edu Oknam Park]<br />
<br />
At Cornell University<br />
* [mailto:dih1@cornell.edu Diane Hillmann]<br />
* [mailto:jp298@cornell.edu Jon Phipps]<br />
<br />
==== Project Links ====<br />
<br />
[[NSDL Registry]] Project<br />
<br />
[[Metadata Management System]]<br />
<br />
[[Research Proposals]] and Projects<br />
<br />
----------<br />
'''''IMPORTANT:''''' Do not cite materials on this Wiki other than for the purposes of collaborating on document creation. This Wiki is intended to be used to work on draft copies of documents. Finished documents will be published, in a persistent and citable form, on the [http://purl.org/NSDLRegistry/ NSDL Registry] Web site. <br />
----------<br />
<br />
Please see [http://meta.wikipedia.org/wiki/MediaWiki_i18n documentation on customizing the interface]<br />
and the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] for usage and configuration help.</div>208.31.47.161http://wiki.metadataregistry.org/Dec._21,_2005Dec. 21, 20052005-12-21T18:38:05Z<p>208.31.47.161: </p>
<hr />
<div>==Telecon Agenda and Notes, Dec. 21, 2005==<br />
<br />
1. Budget that Jon submitted for servers and IP services<br />
# What budget it comes from<br />
# Any other considerations<br />
<br />
2. Reworking the milestones (see: http://phoenix.ischool.washington.edu/wiki/index.php/Revised_Tasks_%26_Milestones)<br />
<br />
3. New doctoral student--Melanie Feinberg (10 week UW Winter Quarter)--versioning (research practicum--RDF modeling)</div>208.31.47.161http://wiki.metadataregistry.org/Revised_Tasks_%26_MilestonesRevised Tasks & Milestones2005-12-21T18:20:44Z<p>208.31.47.161: </p>
<hr />
<div>=Draft Revised Tasks and Milestones=<br />
<br />
<b>MILESTONES:</b><br />
<br />
Year 1:<br />
<br />
''Jan. 31''<br />
#Determine database technology and development language (Jon)<br />
#Implement main storage databases for MMS and Registry (Jon)<br />
<br />
''Feb. 28''<br />
<br />
#Implement Agent registration (Jon)<br />
#Implement Vocabulary description registration (Jon)<br />
#Set up workflow to associate vocabulary descriptions and schemes (Jon & Diane)<br />
<br />
<br />
''Mar. 30''<br />
#Build interface prototypes (search, browse, display) and develop initial feedback loop on prototypes (Jon)<br />
#Determine needs for SKOS information (Diane & Stuart)<br />
#Define validation steps (Diane & Stuart)<br />
#Build interface prototypes (create, update) and develop initial feedback loop on prototypes (Jon)<br />
#Implement creation/updating of terms (Jon)<br />
<br />
''Apr. 30''<br />
#[Begin to involve Betatest Partners]<br />
#Define notification workflow, text, rules, including pending action notification (Diane & Jon)<br />
#Define complete Registry Administrator functionality (Diane & Jon)<br />
<br />
''July 30''<br />
#Implement and test notification (Diane & Jon)<br />
#Define schema registration workflow/data requirements (Stuart & Diane)<br />
#Build Registry administrator interface prototypes (Jon)<br />
<br />
''Aug. 30''<br />
#Build interface prototype (create, update) for schemas and develop initial feedback loop (Jon)<br />
<br />
Year 2:<br />
<br />
''Oct. 2006'' (+12): <br />
#Build interface prototype (create, update) for application profiles and develop initial feedback loop (Jon)<br />
#Develop flash movie/screencast for building APs (Diane & Jon)<br />
<br />
''Nov. 2006''<br />
#Develop requirements for community gathering around vocabularies (Jon, Diane & Stuart)<br />
<br />
<br />
'''Annual Meeting, Nov. 2006''' (+13 mos.): Demonstrable system:<br />
#End user search and display<br />
#Creation of hosted vocabularies within system<br />
#Registration of simple schema<br />
#Flash movie/screencast for building AP</div>208.31.47.161http://wiki.metadataregistry.org/Revised_Tasks_%26_MilestonesRevised Tasks & Milestones2005-12-21T17:17:02Z<p>208.31.47.161: </p>
<hr />
<div>=Draft Revised Tasks and Milestones=<br />
<br />
<b>MILESTONES:</b><br />
<br />
Year 1:<br />
<br />
''Jan. 31''<br />
#Determine database technology and development language (Jon)<br />
#Implement main storage databases for MMS and Registry (Jon)<br />
<br />
''Feb. 28''<br />
<br />
#Implement Agent registration (Jon)<br />
#Implement Vocabulary description registration (Jon)<br />
#Set up workflow to associate vocabulary descriptions and schemes (Jon & Diane)<br />
<br />
<br />
''Mar. 30''<br />
#Build interface prototypes (search, browse, display) and develop initial feedback loop on prototypes (Jon)<br />
#Determine needs for SKOS information (Diane & Stuart)<br />
#Define validation steps (Ryan & Stuart)<br />
<br />
<br />
#Build interface prototypes (create, update) and develop initial feedback loop on prototypes (Jon & Ryan)<br />
#Define notification workflow, text, rules (Diane & Jon & Ryan), including pending action notification (Ryan)<br />
<br />
#[Begin to involve Betatest Partners]<br />
#Implement creation/updating of terms (Jon & Ryan)<br />
<br />
''Apr. 30''<br />
#Implement and test notification (Diane & Jon)<br />
#Define complete Registry Administrator functionality (Diane & Jon)<br />
<br />
''July 30''<br />
#Define schema registration workflow/data requirements (Stuart & Diane)<br />
#Build Registry administrator interface prototypes (Jon)<br />
<br />
''Aug. 30''<br />
#Build interface prototype (create, update) for schemas and develop initial feedback loop (Jon)<br />
<br />
Year 2:<br />
<br />
''Oct. 2006'' (+12): <br />
#Build interface prototype (create, update) for application profiles and develop initial feedback loop (Jon)<br />
#Develop flash movie/screencast for building APs (Diane & Jon)<br />
<br />
''Nov. 2006''<br />
#Develop requirements for community gathering around vocabularies (Jon, Diane & Stuart)<br />
<br />
<br />
'''Annual Meeting, Nov. 2006''' (+13 mos.): Demonstrable system:<br />
#End user search and display<br />
#Creation of hosted vocabularies within system<br />
#Registration of simple schema<br />
#Flash movie/screencast for building AP</div>208.31.47.161http://wiki.metadataregistry.org/Revised_Tasks_%26_MilestonesRevised Tasks & Milestones2005-12-21T16:45:20Z<p>208.31.47.161: </p>
<hr />
<div>=Draft Revised Tasks and Milestones=<br />
<br />
<b>MILESTONES:</b><br />
<br />
Year 1:<br />
<br />
''Jan. 31''<br />
#Determine database technology and development language (Jon)<br />
#Implement main storage databases for MMS and Registry (Jon)<br />
#Implement Agent registration (Jon)<br />
#Implement Vocabulary description registration (Jon)<br />
#Set up workflow to associate vocabulary descriptions and schemes (Jon & Diane & Ryan)<br />
<br />
''Jan. 31''<br />
#[Begin to involve Betatest Partners]<br />
#Build interface prototypes (search, browse, display) and develop initial feedback loop on prototypes (Jon & Ryan)<br />
#Determine needs for SKOS information (Diane & Stuart)<br />
#Define validation steps (Ryan & Stuart)<br />
<br />
''Feb. 28''<br />
#Build interface prototypes (create, update) and develop initial feedback loop on prototypes (Jon & Ryan)<br />
#Define notification workflow, text, rules (Diane & Jon & Ryan), including pending action notification (Ryan)<br />
<br />
''Mar. 30''<br />
#Implement creation/updating of terms (Jon & Ryan)<br />
<br />
''Apr. 30''<br />
#Implement and test notification (Diane & Jon)<br />
#Define complete Registry Administrator functionality (Diane & Jon)<br />
<br />
''July 30''<br />
#Define schema registration workflow/data requirements (Stuart & Diane)<br />
#Build Registry administrator interface prototypes (Jon)<br />
<br />
''Aug. 30''<br />
#Build interface prototype (create, update) for schemas and develop initial feedback loop (Jon)<br />
<br />
Year 2:<br />
<br />
''Oct. 2006'' (+12): <br />
#Build interface prototype (create, update) for application profiles and develop initial feedback loop (Jon)<br />
#Develop flash movie/screencast for building APs (Diane & Jon)<br />
<br />
''Nov. 2006''<br />
#Develop requirements for community gathering around vocabularies (Jon, Diane & Stuart)<br />
<br />
<br />
'''Annual Meeting, Nov. 2006''' (+13 mos.): Demonstrable system:<br />
#End user search and display<br />
#Creation of hosted vocabularies within system<br />
#Registration of simple schema<br />
#Flash movie/screencast for building AP</div>208.31.47.161http://wiki.metadataregistry.org/Revised_Tasks_%26_MilestonesRevised Tasks & Milestones2005-12-21T16:25:42Z<p>208.31.47.161: </p>
<hr />
<div>=Draft Revised Tasks and Milestones=<br />
<br />
<b>MILESTONES:</b><br />
<br />
Year 1:<br />
<br />
''Nov. 30:''<br />
#Determine data store and RDF Libraries (Ryan & Jon)<br />
#Set up 'sandbox' for initial ingest testing (with Oknam's vocabularies) (Ryan & Jon)<br />
#Test queries on ingested data (Ryan & Jon)<br />
#Determine needs for management information about Agents and Vocabulary Descriptions (Diane & Stuart)<br />
#Draft versioning policy (Diane & Stuart)<br />
<br />
''Dec. 31''<br />
#Implement Agent registration (Ryan & Jon)<br />
#Implement Vocabulary description registration (Ryan & Jon)<br />
#Set up workflow to associate vocabulary descriptions and schemes (Jon & Diane & Ryan)<br />
<br />
''Jan. 31''<br />
#[Begin to involve Betatest Partners]<br />
#Build interface prototypes (search, browse, display) and develop initial feedback loop on prototypes (Jon & Ryan)<br />
#Determine needs for SKOS information (Diane & Stuart)<br />
#Define validation steps (Ryan & Stuart)<br />
<br />
''Feb. 28''<br />
#Build interface prototypes (create, update) and develop initial feedback loop on prototypes (Jon & Ryan)<br />
#Define notification workflow, text, rules (Diane & Jon & Ryan), including pending action notification (Ryan)<br />
<br />
''Mar. 30''<br />
#Implement creation/updating of terms (Jon & Ryan)<br />
<br />
''Apr. 30''<br />
#Implement and test notification (Diane & Jon)<br />
#Define complete Registry Administrator functionality (Diane & Jon)<br />
<br />
''July 30''<br />
#Define schema registration workflow/data requirements (Stuart & Diane)<br />
#Build Registry administrator interface prototypes (Jon)<br />
<br />
''Aug. 30''<br />
#Build interface prototype (create, update) for schemas and develop initial feedback loop (Jon)<br />
<br />
Year 2:<br />
<br />
''Oct. 2006'' (+12): <br />
#Build interface prototype (create, update) for application profiles and develop initial feedback loop (Jon)<br />
#Develop flash movie/screencast for building APs (Diane & Jon)<br />
<br />
''Nov. 2006''<br />
#Develop requirements for community gathering around vocabularies (Jon, Diane & Stuart)<br />
<br />
<br />
'''Annual Meeting, Nov. 2006''' (+13 mos.): Demonstrable system:<br />
#End user search and display<br />
#Creation of hosted vocabularies within system<br />
#Registration of simple schema<br />
#Flash movie/screencast for building AP</div>208.31.47.161http://wiki.metadataregistry.org/NSDL_RegistryNSDL Registry2005-12-21T16:25:08Z<p>208.31.47.161: </p>
<hr />
<div>=== An NSDL Registry: Supporting Interoperable Metadata Distribution ===<br />
<br />
What we're about: <i>Building on work in the Dublin Core community on metadata registries, we propose to develop and deploy an NSDL metadata registry (hereafter, ‘the Registry’) to enable collection holders creating metadata for their collections and various applications that generate, consume and process metadata to identify, declare and publish their metadata schemas (element/property sets) and schemes (value spaces/controlled vocabularies) in support of discovery, reuse, standardization and interoperability within NSDL and globally. We proposed to accomplish this task by building on existing work within the communities focused on metadata management issues including the Dublin Core Metadata Initiative (DCMI), the World Wide Web Consortium (W3C), and researchers in networked knowledge organization systems. In particular, we intend to seed development of the Registry with the DCMI Registry open source application. </i><br />
----<br />
[[Timeline of Work]]<br />
----<br />
<br />
[[Working Notes and Documentation]]<br />
<br />
[[Tasks and Milestones]]<br />
<br />
[[Revised Tasks & Milestones]]<br />
<br />
----<br />
<br />
[[Teleconference Agendas and Notes]]<br />
<br />
[[Other Meetings and Notes]]<br />
<br />
<br />
----<br />
<br />
Links:<br />
<br />
----<br />
<br />
Public Pages:<br />
*[http://registry.comm.nsdl.org/cgi-bin/wiki.pl?NSDL_Registry Public Wiki]<br />
*[http://eg2.ischool.washington.edu/registry Registry Web Site]</div>208.31.47.161http://wiki.metadataregistry.org/Dec._21,_2005Dec. 21, 20052005-12-21T16:21:50Z<p>208.31.47.161: </p>
<hr />
<div>==Telecon Agenda and Notes, Dec. 21, 2005==<br />
<br />
1. Budget that Jon submitted for servers and IP services<br />
# What budget it comes from<br />
# Any other considerations<br />
<br />
2.</div>208.31.47.161http://wiki.metadataregistry.org/12/12-13/0512/12-13/052005-12-13T16:49:49Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda & Notes: Meeting, Dec. 12-13, 2005, Jacksonville, NY==<br />
<br />
===Agenda, Monday===<br />
<br />
A. What are our goals for the meeting?<br />
#Resurrect the MMS for the use of GEM and other partners<br />
#* Funding first two months from IMLS evaluation funding<br />
#Provide GEM with a working metadata management system allowing easier ingest and exposure of data and expansion of reach<br />
#Harvest and evaluate UIUC-IMLS data for possible integration with GEM (in time for inclusion into IMLS grant)<br />
#*Possible sustainability option for IMLS data and DLESE?<br />
#Determine <br />
#*What pieces of the overall project will be funded by whom<br />
#*What timelines and deliverables will be needed to move forward efficiently and sensibly, and satisfy our various constituencies<br />
#*Who we will need to collaborate with and how we will manage that collaboration<br />
#*What do we want from the UIUC eval?<br />
#** How does it play with GEM records? Can these records be as useful as current GEM records? If no, why? What would it take to make them work? What would it cost to upgrade them?<br />
#** Diane can create chart<br />
#** Should also include analysis of their collection data<br />
#** UIUC money cannot be used for software, only for personnel (potential six weeks of Jon)<br />
#** NEA money can be used to purchase Spotfire<br />
<br />
B. Review [http://phoenix.ischool.washington.edu/wiki/index.php/Re-implementing_the_MMS Re-implementing the MMS]<br />
#Determine if steps and timelines are appropriate<br />
#*How much will we be implementing for GEM and how much for IMLS? Where is the line?<br />
#** For Phase I, steps 1,5 & 6 will be funded by IMLS-GEM<br />
#** Other pieces of Phase I will be funded by Gateway money<br />
#Determine where partner interaction occurs<br />
#How much interaction will be needed with GEM data partners and who will do it?<br />
#Discussed opportunity with Oracle<br />
#* Oracle funding could finish Phase I, and the majority of Phase II<br />
<br />
C. Scoping out the IMLS grant due Feb. 1<br />
#Lead agency:<br />
#* Prefer Cornell, because Stuart is at his limits<br />
#* Diane will check with Bill and see if a CIS proposal is an option, will also check with Sarah about how much Tom's attitude matters: can CUL be lead agency? Subcontract with GEM?<br />
#Where are matching funds coming from? <br />
#* Cornell indirect contribution <br />
#Research questions:<br />
#* Using user-supplied data for integration in Repository<br />
#* Distributed data networks as sources for K-12 education, how do we bring them on?<br />
#** Privacy considerations, security considerations<br />
#* Diny: It's about push/pull: what has to take place for a classroom teacher to be able to use materials from IMLS in the classroom<br />
#* Diny: How can education agencies and organizations share their resources or information about the use of resources in ways that enhance their value<br />
#* How best can we augment the IMLS records? How does augmenting these increase their value and how can we measure that?<br />
#* How can we improve our processes and distribution to increase the use and value of the resources?<br />
#Challenge is figuring out who will fund what, and how the multiple sources of funding can be leveraged<br />
#Grant will seek funding for all phases, will be supporting GEM exchange, IMLS data, the data distribution network<br />
#* Narrative doesn't need to include all the steps, but will need to be included in the budget and resources<br />
#* Lessons learned from GEM, from NSDL, from UIUC, will be incorporated<br />
#Proposal assumptions:<br />
#* Include pre-collection service provider interactions (a la GEM, NSDL)<br />
#* We will take over the production service component from UIUC<br />
#* Need to move help desk component earlier on the list<br />
#* Include a jump start tool like SPT/CWIS/GEMCAT/Recommender<br />
#* Explain it so people without technical people can understand<br />
<br />
<br />
<br />
Questions<br />
#How to we determine the interactions between the MMS and the RDF datastore maintained by Siderian in the GEM context?<br />
<br />
Jon would like to spend about an hour discussing the NSDL Registry project.</div>208.31.47.161http://wiki.metadataregistry.org/12/12-13/0512/12-13/052005-12-13T16:03:56Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda & Notes: Meeting, Dec. 12-13, 2005, Jacksonville, NY==<br />
<br />
===Agenda, Monday===<br />
<br />
A. What are our goals for the meeting?<br />
#Resurrect the MMS for the use of GEM and other partners<br />
#* Funding first two months from IMLS evaluation funding<br />
#Provide GEM with a working metadata management system allowing easier ingest and exposure of data and expansion of reach<br />
#Harvest and evaluate UIUC-IMLS data for possible integration with GEM (in time for inclusion into IMLS grant)<br />
#*Possible sustainability option for IMLS data and DLESE?<br />
#Determine <br />
#*What pieces of the overall project will be funded by whom<br />
#*What timelines and deliverables will be needed to move forward efficiently and sensibly, and satisfy our various constituencies<br />
#*Who we will need to collaborate with and how we will manage that collaboration<br />
#*What do we want from the UIUC eval?<br />
#** How does it play with GEM records? Can these records be as useful as current GEM records? If no, why? What would it take to make them work? What would it cost to upgrade them?<br />
#** Diane can create chart<br />
#** Should also include analysis of their collection data<br />
#** UIUC money cannot be used for software, only for personnel (potential six weeks of Jon)<br />
#** NEA money can be used to purchase Spotfire<br />
<br />
B. Review [http://phoenix.ischool.washington.edu/wiki/index.php/Re-implementing_the_MMS Re-implementing the MMS]<br />
#Determine if steps and timelines are appropriate<br />
#*How much will we be implementing for GEM and how much for IMLS? Where is the line?<br />
#** For Phase I, steps 1,5 & 6 will be funded by IMLS-GEM<br />
#** Other pieces of Phase I will be funded by Gateway money<br />
#Determine where partner interaction occurs<br />
#How much interaction will be needed with GEM data partners and who will do it?<br />
#Discussed opportunity with Oracle<br />
#* Oracle funding could finish Phase I, and the majority of Phase II<br />
<br />
C. Scoping out the IMLS grant due Feb. 1<br />
#Lead agency:<br />
#* Prefer Cornell, because Stuart is at his limits<br />
#* Diane will check with Bill and see if a CIS proposal is an option, will also check with Sarah about how much Tom's attitude matters: can CUL be lead agency? Subcontract with GEM?<br />
#Where are matching funds coming from? <br />
#* Cornell indirect contribution <br />
#Research questions:<br />
#* Using user-supplied data for integration in Repository<br />
#* Distributed data networks as sources for K-12 education, how do we bring them on?<br />
#** Privacy considerations, security considerations<br />
#* Diny: It's about push/pull: what has to take place for a classroom teacher to be able to use materials from IMLS in the classroom<br />
#* Diny: How can education agencies and organizations share their resources or information about the use of resources in ways that enhance their value<br />
#* How best can we augment the IMLS records? How does augmenting these increase their value and how can we measure that?<br />
#* How can we improve our processes and distribution to increase the use and value of the resources?<br />
#Challenge is figuring out who will fund what, and how the multiple sources of funding can be leveraged<br />
#Grant will seek funding for all phases, will be supporting GEM exchange, IMLS data, the data distribution network<br />
#* Narrative doesn't need to include all the steps, but will need to be included in the budget and resources<br />
#* Lessons learned from GEM, from NSDL, from UIUC, will be incorporated<br />
#Proposal assumptions:<br />
#* Include pre-collection service provider interactions (a la GEM, NSDL)<br />
#* We will take over the production service component from UIUC<br />
#* Need to move help desk component earlier on the list<br />
#* Include a jump start tool like SPT/CWIS/GEMCAT/Recommender<br />
<br />
<br />
<br />
<br />
Questions<br />
#How to we determine the interactions between the MMS and the RDF datastore maintained by Siderian in the GEM context?<br />
<br />
Jon would like to spend about an hour discussing the NSDL Registry project.</div>208.31.47.161http://wiki.metadataregistry.org/12/12-13/0512/12-13/052005-12-13T15:36:41Z<p>208.31.47.161: </p>
<hr />
<div>==Agenda & Notes: Meeting, Dec. 12-13, 2005, Jacksonville, NY==<br />
<br />
===Agenda, Monday===<br />
<br />
A. What are our goals for the meeting?<br />
#Resurrect the MMS for the use of GEM and other partners<br />
#* Funding first two months from IMLS evaluation funding<br />
#Provide GEM with a working metadata management system allowing easier ingest and exposure of data and expansion of reach<br />
#Harvest and evaluate UIUC-IMLS data for possible integration with GEM (in time for inclusion into IMLS grant)<br />
#*Possible sustainability option for IMLS data and DLESE?<br />
#Determine <br />
#*What pieces of the overall project will be funded by whom<br />
#*What timelines and deliverables will be needed to move forward efficiently and sensibly, and satisfy our various constituencies<br />
#*Who we will need to collaborate with and how we will manage that collaboration<br />
#*What do we want from the UIUC eval?<br />
#** How does it play with GEM records? Can these records be as useful as current GEM records? If no, why? What would it take to make them work? What would it cost to upgrade them?<br />
#** Diane can create chart<br />
#** Should also include analysis of their collection data<br />
#** UIUC money cannot be used for software, only for personnel (potential six weeks of Jon)<br />
#** NEA money can be used to purchase Spotfire<br />
<br />
B. Review [http://phoenix.ischool.washington.edu/wiki/index.php/Re-implementing_the_MMS Re-implementing the MMS]<br />
#Determine if steps and timelines are appropriate<br />
#*How much will we be implementing for GEM and how much for IMLS? Where is the line?<br />
#** For Phase I, steps 1,5 & 6 will be funded by IMLS-GEM<br />
#** Other pieces of Phase I will be funded by Gateway money<br />
#Determine where partner interaction occurs<br />
#How much interaction will be needed with GEM data partners and who will do it?<br />
#Discussed opportunity with Oracle<br />
#* Oracle funding could finish Phase I, and the majority of Phase II<br />
<br />
C. Scoping out the IMLS grant due Feb. 1<br />
#Lead agency:<br />
#* Prefer Cornell, because Stuart is at his limits<br />
#* Diane will check with Bill and see if a CIS proposal is an option, will also check with Sarah about how much Tom's attitude matters: can CUL be lead agency? Subcontract with GEM?<br />
#Where are matching funds coming from? <br />
#* Cornell indirect contribution <br />
#Research questions:<br />
#* Using user-supplied data for integration in Repository<br />
#* Distributed data networks as sources for K-12 education, how do we bring them on?<br />
#** Privacy considerations, security considerations<br />
#* Diny: It's about push/pull: what has to take place for a classroom teacher to be able to use materials from IMLS in the classroom<br />
#* Diny: How can education agencies and organizations share their resources or information about the use of resources in ways that enhance their value<br />
#* How best can we augment the IMLS records? How does augmenting these increase their value and how can we measure that?<br />
#* How can we improve our processes and distribution to increase the use and value of the resources?<br />
#Challenge is figuring out who will fund what, and how the multiple sources of funding can be leveraged<br />
#Grant will seek funding for all phases, will be supporting GEM exchange, IMLS data, the data distribution network<br />
#* Narrative doesn't need to include all the steps, but will need to be included in the budget and resources<br />
#* Lessons learned from GEM, from NSDL, from UIUC, will be incorporated<br />
<br />
<br />
Questions<br />
#How to we determine the interactions between the MMS and the RDF datastore maintained by Siderian in the GEM context?<br />
<br />
Jon would like to spend about an hour discussing the NSDL Registry project.</div>208.31.47.161