http://wiki.metadataregistry.org/api.php?action=feedcontributions&user=Sasutton&feedformat=atomMetadata-Registry - User contributions [en]2024-03-29T16:00:03ZUser contributionsMediaWiki 1.22.6http://wiki.metadataregistry.org/Nov._12,_2007Nov. 12, 20072007-11-12T00:32:25Z<p>Sasutton: /* Telecon Agenda & Notes, Monday, Nov. 12, 2007 */</p>
<hr />
<div>=== Telecon Agenda & Notes, Monday, Nov. 12, 2007 ===<br />
<br />
#News from the NSDL Annual Meeting (Jon & Stuart)<br />
#Request for feedback on SKOS proposal (Jon)</div>Sasuttonhttp://wiki.metadataregistry.org/Aug._13,_2007Aug. 13, 20072007-08-12T21:29:06Z<p>Sasutton: New page: * INTEROP status reports</p>
<hr />
<div>* INTEROP status reports</div>Sasuttonhttp://wiki.metadataregistry.org/Teleconference_Agendas_and_NotesTeleconference Agendas and Notes2007-08-12T21:28:19Z<p>Sasutton: /* Teleconference Agendas and Notes */</p>
<hr />
<div>=== Teleconference Agendas and Notes ===<br />
<br />
Calls will be initiated from Seattle.<br />
* [[Aug. 13, 2007]]<br />
* [[Aug. 8, 2007]] Moved to Wed.<br />
* [[July 30, 2007]]<br />
* [[July 23, 2007]] postponed until July 27<br />
* [[July 16, 2007]]<br />
* [[July 9, 2007]] Stuart on vacation<br />
* [[July 2, 2007]] Stuart on the road<br />
* [[June 25, 2007]] Diane at ALA<br />
* [[June 18, 2007]]<br />
* [[June 11, 2007]] Postponed until June 13<br />
* [[June 4, 2007]]<br />
* [[May 29, 2007]]<br />
* [[May 21, 2007]]<br />
* [[May 14, 2007]]<br />
* Apr. 9, 2007-May 7, 2007 Cancelled, everyone traveling<br />
* [[Apr. 2, 2007]]<br />
* [[Mar. 27, 2007]] Cancelled (Stuart in France)<br />
* [[Mar. 19, 2007]] Cancelled (Stuart and Diane in Barcelona)<br />
* [[Mar. 12, 2007]]<br />
* [[Mar. 5, 2007]]<br />
* [[Feb. 26, 2007]]<br />
* [[Feb. 19, 2007]] Cancelled<br />
Telecons moved to Mondays, 8:00 Pacific/11:00 Eastern<br />
* [[Feb. 14, 2007]]<br />
* [[Feb. 7, 2007]]<br />
* [[Jan. 31, 2007]] Cancelled<br />
* [[Jan. 24, 2007]] Cancelled<br />
* [[Jan. 17, 2007]] Cancelled<br />
* [[Jan. 10, 2007]]<br />
* [[Jan. 3, 2007]]<br />
* [[Dec. 21, 2006]] Rescheduled from Wed.<br />
* [[Dec. 13, 2006]]<br />
* [[Dec. 6, 2006]] Rescheduled to Dec. 8<br />
* [[Nov. 29, 2006]]<br />
* [[Nov. 22, 2006]] Cancelled<br />
* [[Nov. 16, 2006]] Moved from Wed. to Thurs.<br />
* [[Nov. 8, 2006]] Cancelled<br />
* [[Nov. 1, 2006]]<br />
* [[Oct. 25, 2006]] Cancelled<br />
* [[Oct. 11, 2006]] Cancelled<br />
* [[Sept. 26, 2006]] Moved from Wed. to Tues.<br />
* [[Sept. 20, 2006]]<br />
* [[Sept. 13, 2006]]<br />
* [[Sept. 6, 2006]] Cancelled<br />
* [[Aug. 30, 2006]]<br />
* [[Aug. 23, 2006]]<br />
* [[Aug. 16, 2006]] Cancelled<br />
* [[Aug. 9, 2006]]<br />
* [[Aug. 4, 2006]] Cancelled<br />
* [[July 26, 2006]] Cancelled<br />
* [[July 21, 2006]] Moved from July 19<br />
* [[July 12, 2006]]<br />
* [[July 5, 2006]]<br />
* [[June 28, 2006]]<br />
* [[June 21, 2006]] Cancelled<br />
* [[June 14, 2006]]<br />
* [[June 7, 2006]]<br />
* [[May 31, 2006]] Cancelled<br />
* [[May 24, 2006]]<br />
* [[May 17, 2006]] Cancelled<br />
* [[May. 3,10 2006]] Cancelled<br />
* [[Apr. 19, 2006]]<br />
* [[Apr. 12, 2006]]<br />
* [[Apr. 5, 2006]]<br />
* [[Mar. 27, 2006]] Moved from Wed. to Monday<br />
* [[Mar. 22, 2006]] Cancelled<br />
* [[Mar. 15, 2006]]<br />
* [[Mar. 8, 2006]] Cancelled<br />
* [[Mar. 3, 2006]] Moved to Friday, then Monday the 6th<br />
* [[Feb. 22, 2006]]<br />
* [[Feb. 15, 2006]] Cancelled: Diane and Stuart at WebWise<br />
* [[Feb. 10, 2006]]<br />
* [[Feb. 1, 2006]]<br />
* [[Jan. 25, 2006]]<br />
* [[Jan. 18, 2006]]<br />
* [[Jan. 11, 2006]] Cancelled<br />
* [[Jan. 4, 2006]]<br />
* [[Dec. 21, 2005]]<br />
* [[Dec. 14, 2005]] Cancelled<br />
* [[Dec. 7, 2005]]<br />
* [[Dec. 1, 2005]]<br />
* [[Oct. 26, 2005]]<br />
* [[Oct. 19, 2005]] Cancelled<br />
* [[Oct. 12, 2005]]<br />
* [[Oct. 5, 2005]]<br />
* [[Oct. 3, 2005]]<br />
* [[Sept. 30, 2005]]<br />
* [[Sept. 21, 2005]]<br />
* Sept. 7 and 14th will be skipped (DC2005 and vacations)<br />
* [[Aug. 31, 2005]] (Stuart will be absent)<br />
* [[Aug. 24, 2005]] <br />
* [[Aug. 17, 2005]] (Jon will be absent)<br />
* [[Aug. 10, 2005]]</div>Sasuttonhttp://wiki.metadataregistry.org/Aug._8,_2007Aug. 8, 20072007-08-07T20:37:20Z<p>Sasutton: </p>
<hr />
<div>* TERMS proposal Cornell wrap-up<br />
** Time to involve Tom Frank<br />
*** Approve budget & budget justification<br />
*** Approve statement of work</div>Sasuttonhttp://wiki.metadataregistry.org/Aug._8,_2007Aug. 8, 20072007-08-07T20:36:43Z<p>Sasutton: New page: * TERMS proposal Cornell wrap-up ** Time to involving Tom Frank *** Approve budget & budget justification *** Approve statement of work</p>
<hr />
<div>* TERMS proposal Cornell wrap-up<br />
** Time to involving Tom Frank<br />
*** Approve budget & budget justification<br />
*** Approve statement of work</div>Sasuttonhttp://wiki.metadataregistry.org/July_30,_2007July 30, 20072007-08-01T14:46:23Z<p>Sasutton: New page: * INTEROP proposal status ** TERMS ** RDA</p>
<hr />
<div>* INTEROP proposal status<br />
** TERMS<br />
** RDA</div>Sasuttonhttp://wiki.metadataregistry.org/July_16,_2007July 16, 20072007-07-15T22:53:44Z<p>Sasutton: </p>
<hr />
<div># Status of registry implementation--End: 9/30/07 (Report 10/1/07)<br />
#* To be accomplished<br />
#* Not to be accomplished<br />
# Singapore<br />
#* DC-Ed Community<br />
#** AP modeling<br />
#**# Inclusion of 'authority' (related issues)<br />
#**# Correlation as related resource<br />
#**#* Use of <tt>conformsTo</tt> or a new <tt>standardCorrelation</tt><br />
#* Registry Community<br />
#* Advisory Board issues<br />
#** Conference location<br />
#** Conference proceedings and other publications<br />
#**# Publication form for DCMI conference proceedings (online/print/CD)<br />
#**# Use of the OJS for publishing proceedings(housed at University of Washington)<br />
#**# Other publications<br />
#**#* ''DCMI Occasional Papers''<br />
# Document/presentation inventory needed for Singapore<br />
#* Proposal document for permanent publishing of DCMI conference proceedings using the OJS {Stuart & Joe}<br />
#* Proposal document for ongoing publication of a new ''DCMI Occasional Papers'' series {Stuart}<br />
#* Proposal document for DCMI conference venues (U.S. & Europe) with educational efforts in other regions {Diane & Stuart }<br />
#* Presentation of correlation resource {Stuart}<br />
#* Presentation on 'authority' in general(?){Diane & Jon}<br />
# Other matters<br />
#* Usage Board: <br />
#** VES/SES {Stuart & Joe}<br />
#** ...<br />
#** ...</div>Sasuttonhttp://wiki.metadataregistry.org/July_16,_2007July 16, 20072007-07-15T22:30:16Z<p>Sasutton: </p>
<hr />
<div># Status of registry implementation--End: 9/30/07 (Report 10/1/07)<br />
# Singapore<br />
#* DC-Ed Community<br />
#** AP modeling<br />
#**# Inclusion of 'authority' (related issues)<br />
#**# Correlation as related resource<br />
#**#* Use of <tt>conformsTo</tt> or a new <tt>standardCorrelation</tt><br />
#* Registry Community<br />
#* Advisory Board issues<br />
#** Conference location<br />
#** Conference proceedings and other publications<br />
#**# Publication form for DCMI conference proceedings (online/print/CD)<br />
#**# Use of the OJS (housed at University of Washington)<br />
#**# Other publications<br />
#**#* ''DCMI Occasional Papers''</div>Sasuttonhttp://wiki.metadataregistry.org/July_16,_2007July 16, 20072007-07-15T22:29:26Z<p>Sasutton: </p>
<hr />
<div># Status of registry implementation--End: 9/30/07 (Report 10/1/07)<br />
# Singapore<br />
#* DC-Ed Community<br />
#** AP modeling<br />
#**# Inclusion of 'authority' (related issues)<br />
#**# Correlation as related resource<br />
#**#* Use of <tt>conformsTo</tt> and a new <tt>standardCorrelation</tt><br />
#* Registry Community<br />
#* Advisory Board issues<br />
#** Conference location<br />
#** Conference proceedings and other publications<br />
#**# Publication form for DCMI conference proceedings (online/print/CD)<br />
#**# Use of the OJS (housed at University of Washington)<br />
#**# Other publications<br />
#**#* ''DCMI Occasional Papers''</div>Sasuttonhttp://wiki.metadataregistry.org/July_16,_2007July 16, 20072007-07-15T22:25:00Z<p>Sasutton: </p>
<hr />
<div>* Status of registry implementation--End: 9/30/07 (Report 10/1/07)<br />
* Singapore<br />
** DC-Ed Community<br />
*** AP modeling<br />
***# Inclusion of 'authority' (related issues)<br />
***# Correlation as related resource<br />
***#* Use of <tt>conformsTo</tt> and a new <tt>standardCorrelation</tt><br />
** Registry Community<br />
** Advisory Board issues<br />
*** Conference location<br />
*** Conference proceedings and other publications<br />
***# Publication form for DCMI conference proceedings (online/print/CD)<br />
***# Use of the OJS (housed at University of Washington)<br />
***# Other publications<br />
***#* ''DCMI Occasional Papers''</div>Sasuttonhttp://wiki.metadataregistry.org/July_16,_2007July 16, 20072007-07-15T22:06:43Z<p>Sasutton: New page: * Status of registry implementation--End: 9/30/07 (Report 10/1/07) * Singapore ** DC-Ed ** Registry</p>
<hr />
<div>* Status of registry implementation--End: 9/30/07 (Report 10/1/07)<br />
* Singapore<br />
** DC-Ed<br />
** Registry</div>Sasuttonhttp://wiki.metadataregistry.org/Apr._2,_2007Apr. 2, 20072007-04-02T13:25:00Z<p>Sasutton: /* Agenda & Notes, April 2, 2007 */</p>
<hr />
<div>===Agenda & Notes, April 2, 2007===<br />
<br />
1. Review of Progress, New Proposal:<br />
* Pin generation (links proposals in FastLane)<br />
* Narrative complete?<br />
* Budget?<br />
** Characterizing CUL work<br />
** Spreadsheet error in including benefit on hourly CUL line<br />
** Justification<br />
* Support letters<br />
** iVia letter expected soon<br />
** Requests sent to Laura Bartolo, Stuart Chalk, Kim Lightle, Bill Arms<br />
** Others? Diny? <br />
<br />
2. Review of Progress, Extension proposal<br />
* Narrative nearing completion?<br />
** 1-page summary for FastLane (Stuart)<br />
* Budget?<br />
** Justification<br />
* Support letters, do we need them? How many?<br />
** We'd thought about asking Tom Baker--any others?<br />
** Letter from Stuart supporting unfunded collaboration (advisor)</div>Sasuttonhttp://wiki.metadataregistry.org/Apr._2,_2007Apr. 2, 20072007-04-02T13:14:49Z<p>Sasutton: </p>
<hr />
<div>===Agenda & Notes, April 2, 2007===<br />
<br />
1. Review of Progress, New Proposal:<br />
* Pin generation (links proposals in FastLane)<br />
* Narrative complete?<br />
* Budget?<br />
** Characterizing CUL work<br />
** Spreadsheet error in including benefit on hourly CUL line<br />
* Support letters<br />
** iVia letter expected soon<br />
** Requests sent to Laura Bartolo, Stuart Chalk, Kim Lightle, Bill Arms<br />
** Others? Diny? <br />
<br />
2. Review of Progress, Extension proposal<br />
* Narrative nearing completion?<br />
** 1-page summary for FastLane (Stuart)<br />
* Budget?<br />
* Support letters, do we need them? How many?<br />
** We'd thought about asking Tom Baker--any others?<br />
** Letter from Stuart supporting unfunded collaboration (advisor)</div>Sasuttonhttp://wiki.metadataregistry.org/Apr._2,_2007Apr. 2, 20072007-04-02T12:57:47Z<p>Sasutton: /* Agenda & Notes, April 2, 2007 */</p>
<hr />
<div>===Agenda & Notes, April 2, 2007===<br />
<br />
1. Review of Progress, New Proposal:<br />
* Pin generation (links proposals in FastLane)<br />
* Narrative complete?<br />
* Budget?<br />
** Characterizing CUL work<br />
** Spreadsheet error in including benefit on hourly CUL line<br />
* Support letters<br />
** iVia letter expected soon<br />
** Requests sent to Laura Bartolo, Stuart Chalk, Kim Lightle, Bill Arms<br />
** Others? Diny? <br />
<br />
2. Review of Progress, Extension proposal<br />
* Narrative nearing completion?<br />
** 1-page summary for FastLane<br />
* Budget?<br />
* Support letters, do we need them? How many?<br />
** We'd thought about asking Tom Baker--any others?<br />
** Letter from Stuart supporting unfunded collaboration (advisor)</div>Sasuttonhttp://wiki.metadataregistry.org/Apr._2,_2007Apr. 2, 20072007-04-02T12:53:48Z<p>Sasutton: /* Agenda & Notes, April 2, 2007 */</p>
<hr />
<div>===Agenda & Notes, April 2, 2007===<br />
<br />
1. Review of Progress, New Proposal:<br />
* Pin generation (links proposals in FastLane)<br />
* Narrative complete?<br />
* Budget?<br />
** Characterizing CUL work<br />
* Support letters<br />
** iVia letter expected soon<br />
** Requests sent to Laura Bartolo, Stuart Chalk, Kim Lightle, Bill Arms<br />
** Others? Diny? <br />
<br />
2. Review of Progress, Extension proposal<br />
* Narrative nearing completion?<br />
** 1-page summary for FastLane<br />
* Budget?<br />
* Support letters, do we need them? How many?<br />
** We'd thought about asking Tom Baker--any others?<br />
** Letter from Stuart supporting unfunded collaboration (advisor)</div>Sasuttonhttp://wiki.metadataregistry.org/Apr._2,_2007Apr. 2, 20072007-04-02T12:50:53Z<p>Sasutton: /* Agenda & Notes, April 2, 2007 */</p>
<hr />
<div>===Agenda & Notes, April 2, 2007===<br />
<br />
1. Review of Progress, New Proposal:<br />
* Pin generation (links proposals in FastLane)<br />
* Narrative complete?<br />
* Budget?<br />
** Characterizing CUL work<br />
* Support letters<br />
** iVia letter expected soon<br />
** Requests sent to Laura Bartolo, Stuart Chalk, Kim Lightle, Bill Arms<br />
** Others? Diny? <br />
<br />
2. Review of Progress, Extension proposal<br />
* Narrative nearing completion?<br />
** 1-page summary<br />
* Budget?<br />
* Support letters, do we need them? How many?<br />
** We'd thought about asking Tom Baker--any others?</div>Sasuttonhttp://wiki.metadataregistry.org/Apr._2,_2007Apr. 2, 20072007-04-02T12:49:34Z<p>Sasutton: /* Agenda & Notes, April 2, 2007 */</p>
<hr />
<div>===Agenda & Notes, April 2, 2007===<br />
<br />
1. Review of Progress, New Proposal:<br />
* Pin generation (links proposals in FastLane)<br />
* Narrative complete?<br />
* Budget?<br />
** Characterizing CUL work<br />
* Support letters<br />
** iVia letter expected soon<br />
** Requests sent to Laura Bartolo, Stuart Chalk, Kim Lightle, Bill Arms<br />
** Others? Diny? <br />
<br />
2. Review of Progress, Extension proposal<br />
* Narrative nearing completion?<br />
* Budget?<br />
* Support letters, do we need them? How many?<br />
** We'd thought about asking Tom Baker--any others?</div>Sasuttonhttp://wiki.metadataregistry.org/Feb._14,_2007Feb. 14, 20072007-02-15T15:54:27Z<p>Sasutton: /* Valentine's Day Telecon and Notes, Feb. 15, 2007 (Moved from 2/14) */</p>
<hr />
<div>===Valentine's Day Telecon and Notes, Feb. 15, 2007 (Moved from 2/14)===<br />
<br />
1. Change in telecon time to accommodate Joe. <br />
<br />
1a. Static on the SKOS list...important? <br />
<br />
2. Diane's discussion with Karen Henry, notes:<br />
* What pathways are trying to gather user annotations (even for local use), does she think they'd be interested in working with us on this. [Ask Kim about this, too]<br />
** Sounds like they still don't know what they're doing with this, going into it very slowly. I brought up the idea we'd had years ago about harvesting them, and she sounded like that was a new idea to her. I pointed out that it was important to be able to categorize them, and the Registry was the tool for that.<br />
* How do they think Expert Voices is going? Are they getting much data? Are they still planning to use the simple model of relating the annotation data, or has something else been developed?<br />
** They're thinking of enabling some limited social tagging for their initial annotation service, so we might add something about relating tags to established vocabularies in our terminology services. <br />
* Are they looking to offload Metadata Harvesting? Or is that seen as something that must be tightly tied to the NDR?<br />
<br />
She was responsive to the notion that the OAI world has not embraced the NDR APIs and that coordinating and scheduling services might be useful.<br />
<br />
4. Where is CI going from here--is there planning for a different administrative structure? How will that be funded? <br />
<br />
5. Ask what the status is with the iVia contract--is that something that NSDL would welcome having us contribute to?<br />
<br />
Sounds like they're putting lots of pressure on Johannes, they think he hasn't been providing much value for the money they've spent. No pathways or projects have been able to use the service. There could be some possibilities here to include something in evaluation (is this collection one that could benefit from iVia services? Or NLP?) as well as in terminology services (maybe use the FAST stuff instead of LCSH, or pull out geographics?<br />
<br />
<br />
3. Proposal discussions:<br />
* Organization and Narrative<br />
* Milestones<br />
* Budget and Overhead<br />
* Tables and images</div>Sasuttonhttp://wiki.metadataregistry.org/F2F_Meeting,_1/24-25/07,_SeattleF2F Meeting, 1/24-25/07, Seattle2007-01-24T18:27:37Z<p>Sasutton: /* NSDL Metadata Services Proposal (New) */</p>
<hr />
<div>===Agenda & Notes, F2F Meeting in Seattle, January 24-25, 2007===<br />
<br />
====NSDL Registry Extension Proposal====<br />
<br />
* Assumptions about what will be complete by Sept. 2007<br />
* Extensions to functionality<br />
** Application profile (including RDF encoding?)<br />
** Distributed registry<br />
* New partnerships?<br />
* Administration<br />
** Stuart as advisor<br />
** Diane as PI<br />
<br />
====NSDL Metadata Services Proposal (New)====<br />
<br />
* The role of CU Library<br />
** Building the MMS<br />
<br />
* The ASN piece<br />
* Administration<br />
** Stuart and Diane as Co-PIs<br />
** UW as "collaborator"<br />
** Cornell as principle<br />
<br />
====Notes====<br />
<br />
* Meaning of "continuing" in the solicitation<br />
<br />
* Integration of Liddy's SAT<br />
<br />
* Do diagram (cloud)<br />
** Terminology services<br />
** Normalization<br />
** Harvesting Management<br />
** iVia<br />
** CNLP SAT</div>Sasuttonhttp://wiki.metadataregistry.org/F2F_Meeting,_1/24-25/07,_SeattleF2F Meeting, 1/24-25/07, Seattle2007-01-24T18:26:01Z<p>Sasutton: /* NSDL Registry Extension Proposal */</p>
<hr />
<div>===Agenda & Notes, F2F Meeting in Seattle, January 24-25, 2007===<br />
<br />
====NSDL Registry Extension Proposal====<br />
<br />
* Assumptions about what will be complete by Sept. 2007<br />
* Extensions to functionality<br />
** Application profile (including RDF encoding?)<br />
** Distributed registry<br />
* New partnerships?<br />
* Administration<br />
** Stuart as advisor<br />
** Diane as PI<br />
<br />
====NSDL Metadata Services Proposal (New)====<br />
<br />
* The role of CU Library<br />
** Building the MMS<br />
<br />
* The ASN piece<br />
<br />
====Notes====<br />
<br />
* Meaning of "continuing" in the solicitation<br />
<br />
* Integration of Liddy's SAT<br />
<br />
* Do diagram (cloud)<br />
** Terminology services<br />
** Normalization<br />
** Harvesting Management<br />
** iVia<br />
** CNLP SAT</div>Sasuttonhttp://wiki.metadataregistry.org/F2F_Meeting,_1/24-25/07,_SeattleF2F Meeting, 1/24-25/07, Seattle2007-01-24T18:23:28Z<p>Sasutton: /* NSDL Registry Extension Proposal */</p>
<hr />
<div>===Agenda & Notes, F2F Meeting in Seattle, January 24-25, 2007===<br />
<br />
====NSDL Registry Extension Proposal====<br />
<br />
* Assumptions about what will be complete by Sept. 2007<br />
* Extensions to functionality<br />
** Application profile (including RDF encoding?)<br />
** Distributed registry<br />
* New partnerships?<br />
<br />
====NSDL Metadata Services Proposal (New)====<br />
<br />
* The role of CU Library<br />
** Building the MMS<br />
<br />
* The ASN piece<br />
<br />
====Notes====<br />
<br />
* Meaning of "continuing" in the solicitation<br />
<br />
* Integration of Liddy's SAT<br />
<br />
* Do diagram (cloud)<br />
** Terminology services<br />
** Normalization<br />
** Harvesting Management<br />
** iVia<br />
** CNLP SAT</div>Sasuttonhttp://wiki.metadataregistry.org/F2F_Meeting,_1/24-25/07,_SeattleF2F Meeting, 1/24-25/07, Seattle2007-01-24T18:13:45Z<p>Sasutton: /* NSDL Metadata Services Proposal (New) */</p>
<hr />
<div>===Agenda & Notes, F2F Meeting in Seattle, January 24-25, 2007===<br />
<br />
====NSDL Registry Extension Proposal====<br />
<br />
* Assumptions about what will be complete by Sept. 2007<br />
* Extensions to functionality<br />
* New partnerships?<br />
<br />
<br />
<br />
====NSDL Metadata Services Proposal (New)====<br />
<br />
* The role of CU Library<br />
** Building the MMS<br />
<br />
* The ASN piece<br />
<br />
====Notes====<br />
<br />
* Meaning of "continuing" in the solicitation<br />
<br />
* Integration of Liddy's SAT<br />
<br />
* Do diagram (cloud)<br />
** Terminology services<br />
** Normalization<br />
** Harvesting Management<br />
** iVia<br />
** CNLP SAT</div>Sasuttonhttp://wiki.metadataregistry.org/Jan._3,_2007Jan. 3, 20072007-01-03T14:32:15Z<p>Sasutton: </p>
<hr />
<div> 1. Discuss Spotfire application--license expires on Jan. 10 and we need to move renewal versions to UW machine.</div>Sasuttonhttp://wiki.metadataregistry.org/Jan._3,_2007Jan. 3, 20072007-01-03T14:31:40Z<p>Sasutton: </p>
<hr />
<div>Discuss Spotfire application--license expires on Jan. 10 and we need to move renewal versions to UW machine.</div>Sasuttonhttp://wiki.metadataregistry.org/Dec._21,_2006Dec. 21, 20062006-12-21T16:59:01Z<p>Sasutton: </p>
<hr />
<div>===Agenda & Notes, December 21, 2006===<br />
<br />
1. Follow-up on last weeks' discussions:<br />
* Update on moving the blog, improving the Registry site (Jon) [Diane will distribute a proposed sitemap]<br />
* Update on working with the Library on the new grant proposals (Diane)<br />
<br />
2. General discussion on DC-Conference issues<br />
* Streaming video, podcasting, etc.<br />
* Should we be setting some milestones to be able to demo some of the AP features in Singapore<br />
<br />
3. Planning for our Seattle meetings<br />
* Agenda<br />
** The Registry Extension<br />
** NSDL Metadata Services<br />
* Participants: Stuart, Jon, Diane, ??<br />
<br />
4. Planning for our DC2007 paper. Some ideas:<br />
* Change management<br />
* Registering Application Profiles<br />
* Considering collaborators (Sam Oh? Alistair?)<br />
<br />
5. Adding the DC Type vocabulary to registry<br />
<br />
6. Report on versioning article</div>Sasuttonhttp://wiki.metadataregistry.org/Dec._21,_2006Dec. 21, 20062006-12-21T15:33:16Z<p>Sasutton: </p>
<hr />
<div>===Agenda & Notes, December 21, 2006===<br />
<br />
1. Follow-up on last weeks' discussions:<br />
* Update on moving the blog, improving the Registry site (Jon) [Diane will distribute a proposed sitemap]<br />
* Update on working with the Library on the new grant proposals (Diane)<br />
<br />
2. General discussion on DC-Conference issues<br />
* Streaming video, podcasting, etc.<br />
* Should we be setting some milestones to be able to demo some of the AP features in Singapore<br />
<br />
3. Planning for our Seattle meetings<br />
* Agenda<br />
** The Registry Extension<br />
** NSDL Metadata Services<br />
* Participants: Stuart, Jon, Diane, ??<br />
<br />
4. Planning for our DC2007 paper. Some ideas:<br />
* Change management<br />
* Registering Application Profiles<br />
* Considering collaborators (Sam Oh? Alistair?)<br />
<br />
5. Adding the DC Type vocabulary to registry</div>Sasuttonhttp://wiki.metadataregistry.org/Main_PageMain Page2006-11-26T14:38:33Z<p>Sasutton: </p>
<hr />
<div>Current Projects --<br />
<br />
&amp;quot;The Partnership&amp;quot;===<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 />
At Cornell University<br />
* [mailto:dih1@cornell.edu Diane Hillmann]<br />
* [mailto:jp298@cornell.edu Jon Phipps]<br />
At University of British Columbia<br />
* [mailto:jtennis@interchange.ubc.ca Joe Tennis]<br />
<br />
==== Project Links <br />
<br />
==== [[NSDL Registry]] Project<br />
<br />
[[Metadata Management System]]<br />
<br />
[[Research Proposals]] and Projects<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. ----------</div>Sasuttonhttp://wiki.metadataregistry.org/Main_PageMain Page2006-11-26T14:27:51Z<p>Sasutton: </p>
<hr />
<div>Current Projects -- &amp;quot;The Partnership&amp;quot; <br />
===At the University of Washington:* <br />
[mailto:sasutton@u.washington.edu Stuart A. Sutton]* [mailto:rjlaundr@u.washington.edu Ryan Laundry]* [mailto:feinberg@u.washington.edu Melanie D. Feinberg]* [mailto:parko.u.washington.edu Oknam Park]At Cornell University* [mailto:dih1@cornell.edu Diane Hillmann]* [mailto:jp298@cornell.edu Jon Phipps]At University of British Columbia* [mailto:jtennis@interchange.ubc.ca Joe Tennis]==== Project Links ====[[NSDL Registry]] Project[[Metadata Management System]][[Research Proposals]] and Projects----------'''''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. ----------</div>Sasuttonhttp://wiki.metadataregistry.org/Main_PageMain Page2006-11-26T14:25:48Z<p>Sasutton: </p>
<hr />
<div>Current Projects -- &amp;quot;The Partnership&amp;quot; ===At the University of Washington:* [mailto:sasutton@u.washington.edu Stuart A. Sutton]* [mailto:rjlaundr@u.washington.edu Ryan Laundry]* [mailto:feinberg@u.washington.edu Melanie D. Feinberg]* [mailto:parko.u.washington.edu Oknam Park]At Cornell University* [mailto:dih1@cornell.edu Diane Hillmann]* [mailto:jp298@cornell.edu Jon Phipps]At University of British Columbia* [mailto:jtennis@interchange.ubc.ca Joe Tennis]==== Project Links ====[[NSDL Registry]] Project[[Metadata Management System]][[Research Proposals]] and Projects----------'''''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. ----------</div>Sasuttonhttp://wiki.metadataregistry.org/Sept._13,_2006Sept. 13, 20062006-09-13T17:49:04Z<p>Sasutton: </p>
<hr />
<div>== Agenda & Notes, Sept. 13, 2006 ==<br />
<br />
1. Changes to the Registry interfaces (Jon)<br />
<br />
2. New Registry features and/or bug fixes (Jon)<br />
<br />
3. The versioning discussion on paper for pre-WG distribution (Joe & Stuart)<br />
* [http://projects.ischool.washington.edu/sasutton/skos/Flow_Chart1.html Flow Charts]<br />
* [http://projects.ischool.washington.edu/sasutton/skos/Concept_History_New.html SKOS Versioning Problem]<br />
<br />
4. Registering Schema and AP properties (Diane)<br />
* A spreadsheet will be distributed before the meeting<br />
<br />
5. Timetables for DC2006 draft presentation slides for review<br />
* Paper presentation (9/20)<br />
* WG demo and presentation (9/22)<br />
<br />
6. The [http://eg2.ischool.washington.edu/registry Project page]<br />
* Is woefully out of date<br />
* The blog is broken<br />
* Needs to be updated and beefed up before the DC and NSDL Annual meetings</div>Sasuttonhttp://wiki.metadataregistry.org/F2F_Meeting,_4/27/06,_SeattleF2F Meeting, 4/27/06, Seattle2006-04-27T02:28:49Z<p>Sasutton: /* Meeting Agenda and Notes, 4/27/06, Seattle */</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 />
* Budget expectations?<br />
** Immediate funding<br />
* Assistance needs?<br />
* Do we need a formal contract? If so, what are it's components?<br />
<br />
3. GEM cataloging/augmentation services<br />
<br />
* How will they operate?<br />
** Short-term (Immediate needs)<br />
*** Current Consortium Members needing update (GEM XML schema (new) or GEM RDF/XML schema)<br />
*** NEA affilliates--Kentucky & Connecticut<br />
** Long-term<br />
* Who will run them?<br />
** Short-term<br />
** Long-term<br />
* What tools will they need?<br />
** Short-term<br />
** Long-term</div>Sasuttonhttp://wiki.metadataregistry.org/F2F_Meeting,_4/27/06,_SeattleF2F Meeting, 4/27/06, Seattle2006-04-27T00:59:41Z<p>Sasutton: /* Meeting Agenda and Notes, 4/27/06, Seattle */</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 />
* Budget expectations?<br />
* Assistance needs?<br />
* Do we need a formal contract? If so, what are it's components?<br />
<br />
3. GEM cataloging/augmentation services<br />
<br />
* How will they operate?<br />
** Short-term (Immediate needs)<br />
*** Current Consortium Members needing update (GEM XML schema (new) or GEM RDF/XML schema)<br />
*** NEA affilliates--Kentucky & Connecticut<br />
** Long-term<br />
* Who will run them?<br />
** Short-term<br />
** Long-term<br />
* What tools will they need?<br />
** Short-term<br />
** Long-term</div>Sasuttonhttp://wiki.metadataregistry.org/F2F_Meeting,_4/27/06,_SeattleF2F Meeting, 4/27/06, Seattle2006-04-26T23:53:57Z<p>Sasutton: /* Meeting Agenda and Notes, 4/27/06, Seattle */</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 />
* Budget expectations?<br />
* Assistance needs?<br />
* Do we need a formal contract? If so, what are it's components?<br />
<br />
3. GEM cataloging/augmentation services<br />
<br />
* How will they operate?<br />
** Short-term (Immediate needs)<br />
*** Current Consortium Members needing update (GEM XML schema or GEM RDF/XML schema)<br />
*** NEA affilliates--Kentucky & Connecticut<br />
** Long-term<br />
* Who will run them?<br />
** Short-term<br />
** Long-term<br />
* What tools will they need?<br />
** Short-term<br />
** Long-term</div>Sasuttonhttp://wiki.metadataregistry.org/F2F_Meeting,_4/27/06,_SeattleF2F Meeting, 4/27/06, Seattle2006-04-26T23:52:32Z<p>Sasutton: /* Meeting Agenda and Notes, 4/27/06, Seattle */</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 />
* Budget expectations?<br />
* Assistance needs?<br />
* Do we need a formal contract? If so, what are it's components?<br />
<br />
3. GEM cataloging/augmentation services<br />
<br />
* How will they operate?<br />
** Short-term (Immediate needs)<br />
*** Current Consortium Members needing update (GEM XML schema or GEM RDF/XML schema)<br />
*** NEA affilliates--Kentucky<br />
** Long-term<br />
* Who will run them?<br />
** Short-term<br />
** Long-term<br />
* What tools will they need?<br />
** Short-term<br />
** Long-term</div>Sasuttonhttp://wiki.metadataregistry.org/F2F_Meeting,_4/27/06,_SeattleF2F Meeting, 4/27/06, Seattle2006-04-26T23:10:59Z<p>Sasutton: /* Meeting Agenda and Notes, 4/27/06, Seattle */</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 />
** Short-term<br />
** Long-term<br />
* Who will run them?<br />
* What tools will they need?</div>Sasuttonhttp://wiki.metadataregistry.org/F2F_Meeting,_4/27/06,_SeattleF2F Meeting, 4/27/06, Seattle2006-04-26T23:10:07Z<p>Sasutton: /* Meeting Agenda and Notes, 4/27/06, Seattle */</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 />
** Short-term<br />
* Who will run them?<br />
* What tools will they need?</div>Sasuttonhttp://wiki.metadataregistry.org/F2F_Meeting,_4/27/06,_SeattleF2F Meeting, 4/27/06, Seattle2006-04-26T23:08:47Z<p>Sasutton: /* Meeting Agenda and Notes, 4/27/06, Seattle */</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 />
* Short-term<br />
* Who will run them?<br />
* What tools will they need?</div>Sasuttonhttp://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-20T18:23:52Z<p>Sasutton: /* Agenda */</p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
=== Preface ===<br />
<br />
The goals of this technical meeting are two-fold: (1) so that each of the participants can become familiar with the functionality and implementation of the technologies each has developed (ASAS & ASN (Damon), MMS (Jon), Plone/Seamark & ASN URI Resolver (Ryan)); and (2) to look to issues of interoperability among these applications. It is our intention that these applications: (1) interoperate, and (2) not duplicate functionality unnecessarily. <br />
<br />
In essence: <br />
<br />
1. We see the Metadata Management System (MMS) as the set of functions that handle metadata for the Gateway environment.<br />
<br />
* Manages external metadata feeds (aggregation) into the GEM environment (e.g., Consortium member feeds & other OAI feeds);<br />
* Manages metadata transformations and augmentation; <br />
* Manages metadata export to both the Plone/Seamark environment and the ASAS; and<br />
* Manages internal metadata feeds of augmented metadata generated within the Plone/Seamark and ASAS environments.<br />
<br />
2. We see the GEM Gateway for 21st Century Skills as serving its traditionl portal functions with the addition of annotations by various member classes (Gemologists, GEM Members etc.) as well as personalization systems.<br />
<br />
* Manages GEM membership functions<br />
* Manages workflow and internal data management for all GEM authoring services (annotations, content development)<br />
* Uses the MMS as base metadata repository: (1) ingests GEM RDF metadata instances from the MMS repository; and (2)outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
3. We see the ASAS as the point-of-presence of GEM in the K-12 environment.<br />
<br />
* Uses the MMS as base metadata repository: (1)ingests GEM RDF metadata instances from the MMS repository; and (2) outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
Presenters should feel free to distribute links and documentation prior to the meeting.<br />
<br />
=== Agenda ===<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 />
* GEM Annotation system<br />
<br />
2. Presentation: Damon Gravning<br />
<br />
* Technical overview of current ASN processes for ingesting and maintaining data<br />
* ASAS and an 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--Note: discuss 'mudball'-to-reified RDF in Gateway)</div>Sasuttonhttp://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-20T18:19:35Z<p>Sasutton: /* Agenda */</p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
=== Preface ===<br />
<br />
The goals of this technical meeting are two-fold: (1) so that each of the participants can become familiar with the functionality and implementation of the technologies each has developed (ASAS & ASN (Damon), MMS (Jon), Plone/Seamark & ASN URI Resolver (Ryan)); and (2) to look to issues of interoperability among these applications. It is our intention that these applications: (1) interoperate, and (2) not duplicate functionality unnecessarily. <br />
<br />
In essence: <br />
<br />
1. We see the Metadata Management System (MMS) as the set of functions that handle metadata for the Gateway environment.<br />
<br />
* Manages external metadata feeds (aggregation) into the GEM environment (e.g., Consortium member feeds & other OAI feeds);<br />
* Manages metadata transformations and augmentation; <br />
* Manages metadata export to both the Plone/Seamark environment and the ASAS; and<br />
* Manages internal metadata feeds of augmented metadata generated within the Plone/Seamark and ASAS environments.<br />
<br />
2. We see the GEM Gateway for 21st Century Skills as serving its traditionl portal functions with the addition of annotations by various member classes (Gemologists, GEM Members etc.) as well as personalization systems.<br />
<br />
* Manages GEM membership functions<br />
* Manages workflow and internal data management for all GEM authoring services (annotations, content development)<br />
* Uses the MMS as base metadata repository: (1) ingests GEM RDF metadata instances from the MMS repository; and (2)outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
3. We see the ASAS as the point-of-presence of GEM in the K-12 environment.<br />
<br />
* Uses the MMS as base metadata repository: (1)ingests GEM RDF metadata instances from the MMS repository; and (2) outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
Presenters should feel free to distribute links and documentation prior to the meeting.<br />
<br />
=== Agenda ===<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 />
* GEM Annotation system<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 including ASAS<br />
<br />
3. Presentation: Jon Phipps<br />
<br />
* Metadata Management System requirements and functionality<br />
* Augmented Metadata requirements (with 'mudball' schema example--Note: discuss 'mudball'-to-reified RDF in Gateway)</div>Sasuttonhttp://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-20T18:19:02Z<p>Sasutton: /* Agenda */</p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
=== Preface ===<br />
<br />
The goals of this technical meeting are two-fold: (1) so that each of the participants can become familiar with the functionality and implementation of the technologies each has developed (ASAS & ASN (Damon), MMS (Jon), Plone/Seamark & ASN URI Resolver (Ryan)); and (2) to look to issues of interoperability among these applications. It is our intention that these applications: (1) interoperate, and (2) not duplicate functionality unnecessarily. <br />
<br />
In essence: <br />
<br />
1. We see the Metadata Management System (MMS) as the set of functions that handle metadata for the Gateway environment.<br />
<br />
* Manages external metadata feeds (aggregation) into the GEM environment (e.g., Consortium member feeds & other OAI feeds);<br />
* Manages metadata transformations and augmentation; <br />
* Manages metadata export to both the Plone/Seamark environment and the ASAS; and<br />
* Manages internal metadata feeds of augmented metadata generated within the Plone/Seamark and ASAS environments.<br />
<br />
2. We see the GEM Gateway for 21st Century Skills as serving its traditionl portal functions with the addition of annotations by various member classes (Gemologists, GEM Members etc.) as well as personalization systems.<br />
<br />
* Manages GEM membership functions<br />
* Manages workflow and internal data management for all GEM authoring services (annotations, content development)<br />
* Uses the MMS as base metadata repository: (1) ingests GEM RDF metadata instances from the MMS repository; and (2)outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
3. We see the ASAS as the point-of-presence of GEM in the K-12 environment.<br />
<br />
* Uses the MMS as base metadata repository: (1)ingests GEM RDF metadata instances from the MMS repository; and (2) outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
Presenters should feel free to distribute links and documentation prior to the meeting.<br />
<br />
=== Agenda ===<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 />
* GEM Annotation system<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--Note: discuss 'mudball'-to-reified RDF in Gateway)</div>Sasuttonhttp://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-20T18:17:11Z<p>Sasutton: /* Preface */</p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
=== Preface ===<br />
<br />
The goals of this technical meeting are two-fold: (1) so that each of the participants can become familiar with the functionality and implementation of the technologies each has developed (ASAS & ASN (Damon), MMS (Jon), Plone/Seamark & ASN URI Resolver (Ryan)); and (2) to look to issues of interoperability among these applications. It is our intention that these applications: (1) interoperate, and (2) not duplicate functionality unnecessarily. <br />
<br />
In essence: <br />
<br />
1. We see the Metadata Management System (MMS) as the set of functions that handle metadata for the Gateway environment.<br />
<br />
* Manages external metadata feeds (aggregation) into the GEM environment (e.g., Consortium member feeds & other OAI feeds);<br />
* Manages metadata transformations and augmentation; <br />
* Manages metadata export to both the Plone/Seamark environment and the ASAS; and<br />
* Manages internal metadata feeds of augmented metadata generated within the Plone/Seamark and ASAS environments.<br />
<br />
2. We see the GEM Gateway for 21st Century Skills as serving its traditionl portal functions with the addition of annotations by various member classes (Gemologists, GEM Members etc.) as well as personalization systems.<br />
<br />
* Manages GEM membership functions<br />
* Manages workflow and internal data management for all GEM authoring services (annotations, content development)<br />
* Uses the MMS as base metadata repository: (1) ingests GEM RDF metadata instances from the MMS repository; and (2)outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
3. We see the ASAS as the point-of-presence of GEM in the K-12 environment.<br />
<br />
* Uses the MMS as base metadata repository: (1)ingests GEM RDF metadata instances from the MMS repository; and (2) outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
Presenters should feel free to distribute links and documentation prior to the meeting.<br />
<br />
=== Agenda ===<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 />
* GEM Annotation system<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>Sasuttonhttp://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-20T18:15:56Z<p>Sasutton: /* Preface */</p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
=== Preface ===<br />
<br />
The goals of this technical meeting are two-fold: (1) so that each of the participants can become familiar with the functionality and implementation of the technologies each has developed (ASAS & ASN (Damon), MMS (Jon), Plone/Seamark & ASN URI Resolver (Ryan)); and (2) to look to issues of interoperability among these applications. It is our intention that these applications: (1) interoperate, and (2) not duplicate functionality unnecessarily. <br />
<br />
In essence: <br />
<br />
1. We see the Metadata Management System (MMS) as the set of functions that handle metadata for the Gateway environment.<br />
<br />
* Manages external metadata feeds (aggregation) into the GEM environment (e.g., Consortium member feeds & other OAI feeds);<br />
* Manages metadata transformations and augmentation; <br />
* Manages metadata export to both the Plone/Seamark environment and the ASAS; and<br />
* Manages internal metadata feeds of augmented metadata generated within the Plone/Seamark and ASAS environments.<br />
<br />
2. We see the GEM Gateway for 21st Century Skills as serving its traditionl portal functions with the addition of annotations by various member classes (Gemologists, GEM Members etc.) as well as personalization systems.<br />
<br />
* Manages GEM membership functions<br />
* Manages workflow and internal data management for all GEM authoring services (annotations, content development)<br />
* Uses the MMS as base metadata repository<br />
** Ingests GEM RDF metadata instances from the MMS repository<br />
** Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
3. We see the ASAS as the point-of-presence of GEM in the K-12 environment.<br />
<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
Presenters should feel free to distribute links and documentation prior to the meeting.<br />
<br />
=== Agenda ===<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 />
* GEM Annotation system<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>Sasuttonhttp://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-20T18:15:24Z<p>Sasutton: /* Preface */</p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
=== Preface ===<br />
<br />
The goals of this technical meeting are two-fold: (1) so that each of the participants can become familiar with the functionality and implementation of the technologies each has developed (ASAS & ASN (Damon), MMS (Jon), Plone/Seamark & ASN URI Resolver (Ryan)); and (2) to look to issues of interoperability among these applications. It is our intention that these applications: (1) interoperate, and (2) not duplicate functionality unnecessarily. <br />
<br />
In essence: <br />
<br />
1. We see the Metadata Management System (MMS) as the set of functions that handle metadata for the Gateway environment.<br />
<br />
* Manages external metadata feeds (aggregation) into the GEM environment (e.g., Consortium member feeds & other OAI feeds);<br />
* Manages metadata transformations and augmentation; <br />
* Manages metadata export to both the Plone/Seamark environment and the ASAS; and<br />
* Manages internal metadata feeds of augmented metadata generated within the Plone/Seamark and ASAS environments.<br />
<br />
2. We see the GEM Gateway for 21st Century Skills as serving its traditionl portal functions with the addition of annotations by various member classes (Gemologists, GEM Members etc.) as well as personalization systems.<br />
<br />
* Manages GEM membership functions<br />
* Manages workflow and internal data management for all GEM authoring services (annotations, content development)<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
3. We see the ASAS as the point-of-presence of GEM in the K-12 environment.<br />
<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
Presenters should feel free to distribute links and documentation prior to the meeting.<br />
<br />
=== Agenda ===<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 />
* GEM Annotation system<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>Sasuttonhttp://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-20T18:14:34Z<p>Sasutton: /* Preface */</p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
=== Preface ===<br />
<br />
The goals of this technical meeting are two-fold: (1) so that each of the participants can become familiar with the functionality and implementation of the technologies each has developed (ASAS & ASN (Damon), MMS (Jon), Plone/Seamark & ASN URI Resolver (Ryan)); and (2) to look to issues of interoperability among these applications. It is our intention that these applications: (1) interoperate, and (2) not duplicate functionality unnecessarily. <br />
<br />
In essence: <br />
<br />
1. We see the Metadata Management System (MMS) as the set of functions that handle metadata for the Gateway environment.<br />
<br />
* Manages external metadata feeds (aggregation) into the GEM environment (e.g., Consortium member feeds & other OAI feeds);<br />
* Manages metadata transformations and augmentation; <br />
* Manages metadata export to both the Plone/Seamark environment and the ASAS; and<br />
* Manages internal metadata feeds of augmented metadata generated within the Plone/Seamark and ASAS environment.<br />
<br />
2. We see the GEM Gateway for 21st Century Skills as serving its traditionl portal functions with the addition of annotations by various member classes (Gemologists, GEM Members etc.) as well as personalization systems.<br />
<br />
* Manages GEM membership functions<br />
* Manages workflow and internal data management for all GEM authoring services (annotations, content development)<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
3. We see the ASAS as the point-of-presence of GEM in the K-12 environment.<br />
<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
Presenters should feel free to distribute links and documentation prior to the meeting.<br />
<br />
=== Agenda ===<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 />
* GEM Annotation system<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>Sasuttonhttp://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-20T18:13:34Z<p>Sasutton: /* Preface */</p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
=== Preface ===<br />
<br />
The goals of this technical meeting are two-fold: (1) so that each of the participants can become familiar with the functionality and implementation of the technologies each has developed (ASAS & ASN (Damon), MMS (Jon), Plone/Seamark & ASN URI Resolver (Ryan)); and (2) to look to issues of interoperability among these applications. It is our intention that these applications: (1) interoperate, and (2) not duplicate functionality unnecessarily. <br />
<br />
In essence: <br />
<br />
1. We see the Metadata Management System (MMS) as the set of functions that handle metadata for the Gateway environment.<br />
<br />
* Manages external metadata feeds (aggregation) into the GEM environment (e.g., Consortium member feeds);<br />
* Manages metadata transformations and augmentation; <br />
* Manages metadata export to both the Plone/Seamark environment and the ASAS; and<br />
* Manages internal metadata feeds of augmented metadata generated within the Plone/Seamark and ASAS environment.<br />
<br />
2. We see the GEM Gateway for 21st Century Skills as serving its traditionl portal functions with the addition of annotations by various member classes (Gemologists, GEM Members etc.) as well as personalization systems.<br />
<br />
* Manages GEM membership functions<br />
* Manages workflow and internal data management for all GEM authoring services (annotations, content development)<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
3. We see the ASAS as the point-of-presence of GEM in the K-12 environment.<br />
<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
Presenters should feel free to distribute links and documentation prior to the meeting.<br />
<br />
=== Agenda ===<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 />
* GEM Annotation system<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>Sasuttonhttp://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-20T18:13:09Z<p>Sasutton: /* Preface */</p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
=== Preface ===<br />
<br />
The goals of this technical meeting are two-fold: (1) so that each of the participants can become familiar with the functionality and implementation of the technologies you have developed (ASAS & ASN (Damon), MMS (Jon), Plone/Seamark & ASN URI Resolver (Ryan)); and (2) to look to issues of interoperability among these applications. It is our intention that these applications: (1) interoperate, and (2) not duplicate functionality unnecessarily. <br />
<br />
In essence: <br />
<br />
1. We see the Metadata Management System (MMS) as the set of functions that handle metadata for the Gateway environment.<br />
<br />
* Manages external metadata feeds (aggregation) into the GEM environment (e.g., Consortium member feeds);<br />
* Manages metadata transformations and augmentation; <br />
* Manages metadata export to both the Plone/Seamark environment and the ASAS; and<br />
* Manages internal metadata feeds of augmented metadata generated within the Plone/Seamark and ASAS environment.<br />
<br />
2. We see the GEM Gateway for 21st Century Skills as serving its traditionl portal functions with the addition of annotations by various member classes (Gemologists, GEM Members etc.) as well as personalization systems.<br />
<br />
* Manages GEM membership functions<br />
* Manages workflow and internal data management for all GEM authoring services (annotations, content development)<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
3. We see the ASAS as the point-of-presence of GEM in the K-12 environment.<br />
<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
Presenters should feel free to distribute links and documentation prior to the meeting.<br />
<br />
=== Agenda ===<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 />
* GEM Annotation system<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>Sasuttonhttp://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-20T18:12:48Z<p>Sasutton: /* Preface */</p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
=== Preface ===<br />
<br />
The goal of this technical meeting is two-fold: (1) so that each of the participants can become familiar with the functionality and implementation of the technologies you have developed (ASAS & ASN (Damon), MMS (Jon), Plone/Seamark & ASN URI Resolver (Ryan)); and (2) to look to issues of interoperability among these applications. It is our intention that these applications: (1) interoperate, and (2) not duplicate functionality unnecessarily. <br />
<br />
In essence: <br />
<br />
1. We see the Metadata Management System (MMS) as the set of functions that handle metadata for the Gateway environment.<br />
<br />
* Manages external metadata feeds (aggregation) into the GEM environment (e.g., Consortium member feeds);<br />
* Manages metadata transformations and augmentation; <br />
* Manages metadata export to both the Plone/Seamark environment and the ASAS; and<br />
* Manages internal metadata feeds of augmented metadata generated within the Plone/Seamark and ASAS environment.<br />
<br />
2. We see the GEM Gateway for 21st Century Skills as serving its traditionl portal functions with the addition of annotations by various member classes (Gemologists, GEM Members etc.) as well as personalization systems.<br />
<br />
* Manages GEM membership functions<br />
* Manages workflow and internal data management for all GEM authoring services (annotations, content development)<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
3. We see the ASAS as the point-of-presence of GEM in the K-12 environment.<br />
<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
Presenters should feel free to distribute links and documentation prior to the meeting.<br />
<br />
<br />
=== Agenda ===<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 />
* GEM Annotation system<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>Sasuttonhttp://wiki.metadataregistry.org/Technical_F2F_Meeting,_4/26/06Technical F2F Meeting, 4/26/062006-04-20T18:12:11Z<p>Sasutton: /* Technical Meeting, Wednesday, 4/26/06 */</p>
<hr />
<div>== Technical Meeting, Wednesday, 4/26/06 ==<br />
<br />
Attending: Jon Phipps, Ryan Laundry, Damon Gravning<br />
<br />
= Preface =<br />
<br />
The goal of this technical meeting is two-fold: (1) so that each of the participants can become familiar with the functionality and implementation of the technologies you have developed (ASAS & ASN (Damon), MMS (Jon), Plone/Seamark & ASN URI Resolver (Ryan)); and (2) to look to issues of interoperability among these applications. It is our intention that these applications: (1) interoperate, and (2) not duplicate functionality unnecessarily. <br />
<br />
In essence: <br />
<br />
1. We see the Metadata Management System (MMS) as the set of functions that handle metadata for the Gateway environment.<br />
<br />
* Manages external metadata feeds (aggregation) into the GEM environment (e.g., Consortium member feeds);<br />
* Manages metadata transformations and augmentation; <br />
* Manages metadata export to both the Plone/Seamark environment and the ASAS; and<br />
* Manages internal metadata feeds of augmented metadata generated within the Plone/Seamark and ASAS environment.<br />
<br />
2. We see the GEM Gateway for 21st Century Skills as serving its traditionl portal functions with the addition of annotations by various member classes (Gemologists, GEM Members etc.) as well as personalization systems.<br />
<br />
* Manages GEM membership functions<br />
* Manages workflow and internal data management for all GEM authoring services (annotations, content development)<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
3. We see the ASAS as the point-of-presence of GEM in the K-12 environment.<br />
<br />
* Uses the MMS as base metadata repository<br />
* Ingests GEM RDF metadata instances from the MMS repository<br />
* Outputs augmented GEM metadata instances (e.g., associated annotations) to the MMS reporsitory<br />
<br />
Presenters should feel free to distribute links and documentation prior to the meeting.<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 />
* GEM Annotation system<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>Sasuttonhttp://wiki.metadataregistry.org/Working_Notes_and_DocumentationWorking Notes and Documentation2006-02-09T21:54:32Z<p>Sasutton: /* SKOS Documents */</p>
<hr />
<div>===Working Documents===<br />
<br />
*[http://eg2.ischool.washington.edu/registry/documents/proposalDocs/ Registry Proposal Documents] Registry proposal documents submitted to NSF<br />
<br />
*[http://www.ukoln.ac.uk/projects/iemsr/background/ Good start on a bibliography, from JISC]<br />
<br />
====NSDL Registry Use Cases====<br />
<br />
*[[General Use Case Information]]<br />
<br />
*[[NSDL Registry Use Case Documentation (Vocabularies)]]<br />
<br />
*[[NSDL Registry Use Case Documentation (Schemas)]] <br />
<br />
*[[NSDL Registry Use Cases (Application Profiles)]]<br />
<br />
*[[NSDL Registry Use Cases (Schema Crosswalk)]]<br />
<br />
*[[NSDL Registry Use Cases (Scheme Semantic Mapping)]]<br />
<br />
====Functional Requirements====<br />
<br />
*[[NSDL Registry Functional Requirements]]<br />
<br />
*[[Versioning]]<br />
<br />
*[[Plone Products]]<br />
<br />
===Reference Documents===<br />
<br />
====SKOS Documents====<br />
[http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102/ SKOS Core Guide]<br />
<br />
[http://www.w3.org/TR/2005/WD-swbp-skos-core-spec-20051102/ SKOS Core Vocabulary Specification]<br />
<br />
[http://www.w3.org/TR/2005/WD-swbp-thesaurus-pubguide-20050517/ Quick Guide to Publishing a Thesaurus on the Semantic Web]<br />
<br />
[http://esw.w3.org/topic/SkosDev SKOS Development Wiki]<br />
<br />
[http://www.w3.org/2004/02/skos/mapping/spec/ SKOS Mapping Vocabulary Specification]<br />
<br />
[http://www.w3c.rl.ac.uk/SWAD/deliverables/8.4.html Inter-Thesaurus Mapping]<br />
<br />
[http://www.w3.org/2001/sw/Europe/reports/thes/skosapi.html SKOS API]<br />
<br />
====Other Reference Documents====<br />
<br />
[http://metadata-standards.org/11179/ Home page for ISO11179-Metadata Registries]<br />
<br />
[http://delos-noe.iei.pi.cnr.it/activities/standardizationforum/Registries.pdf Principles of Metadata Registries/Tom Baker]<br />
<br />
===Annual Meeting Planning===<br />
<br />
* [[Annual Meeting Agenda]]<br />
<br />
* [[Annual Meeting Announcement]]<br />
<br />
* [http://phoenix.ischool.washington.edu/wiki/index.php/Candidate_List_of_Vocabularies Proposed Candidate List of Vocabularies]<br />
<br />
* [http://phoenix.ischool.washington.edu/wiki/index.php?title=Proposed_Project_Survey Proposed Project Survey]<br />
<br />
=== Vocabularies in SKOS ===<br />
<br />
* [http://eg2.ischool.washington.edu/registry/documents/vocExamples/folder.2005-10-26.7157717327/ NSDL Resource Type Vocabulary]<br />
<br />
* [http://eg2.ischool.washington.edu/registry/documents/vocExamples/folder.2005-10-26.3515496026/ ENCdl Vocubularies]<br />
<br />
* [http://eg2.ischool.washington.edu/registry/documents/vocExamples/animal-behavior-vocabulary/ Animal Behavior Vocabulary]<br />
<br />
* [http://eg2.ischool.washington.edu/registry/documents/vocExamples/kmoddl-type-vocabulary/ KMODDL Type Vocabulary]<br />
<br />
* [http://eg2.ischool.washington.edu/registry/documents/vocExamples/parko/ GEM Vocabularies in SKOS]<br />
<br />
* [http://eg2.ischool.washington.edu/registry/documents/vocExamples/folder.2005-10-26.6183119083/ GEM Vocabularies in OWL]<br />
<br />
* [http://eg2.ischool.washington.edu/registry/documents/vocExamples/folder.2005-10-26.1289004633/ Vocabularies Mapping]<br />
<br />
===Evaluation Planning===<br />
<br />
===Replaced Pages (Archived Pages)===<br />
<br />
[[Original Task List Draft]]</div>Sasuttonhttp://wiki.metadataregistry.org/Feb._10,_2006Feb. 10, 20062006-02-09T16:24:33Z<p>Sasutton: </p>
<hr />
<div>== Agenda ==<br />
1. Discuss current state of GEM metadata feeds (see below)<br />
<br />
2. Discuss MMS integration (per Diane/Jon emails)<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</div>Sasuttonhttp://wiki.metadataregistry.org/Feb._10,_2006Feb. 10, 20062006-02-09T16:23:46Z<p>Sasutton: </p>
<hr />
<div>== Agenda ==<br />
1. Discuss current state of GEM metadata feeds (see below)<br />
<br />
2. Discuss MMS integration (per Diane/Jon emails)<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 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</div>Sasutton