changes.
| | [Described Project Activities] |
| | |
| | h1. Draft Project Plan for Registry Experiment |
| | |
| | | *I. Goals / Activities * |
| | | *I. Goals / Activities* |
| | |
| | # Advertise the collections in the NSDL that are aggregated by the Core Integration Project |
| | # Import the Records from the IESR into the Ockham Registry |
| | # NSDL Core Integration will experiment in using the registry as a knowledgebase for its aggregation activities |
| | # NSDL Core Integration will advertise its available services in the registry |
| | # Recommender project will experiment in using the registry to discover new collections with which to work |
| | # Recommender project will advertise their service and identify potential "sub-services" to also advertise |
| | # LinkingOpenCourseWare will experiment in using the registry to discover, locate, and automatically configure collections for use in a content-based recommender system focused on recommending content for courses, and vice-versa |
| | # LinkingOpenCourseWare will advertise its available services in the registry |
| | # Skolr/ARLO will experiment in using the registry.... |
| | # Emory will experiment in using the registry for its transformation services |
| | |
| | *II. Participants* |
| | |
| | The Ockham Initiative |
| | IESR |
| | NSDL Core Integration |
| | Recommender Project |
| | LinkingOpenCourseWare Project |
| | Sklor/ARLO Project |
| | |
| | |
| | |
| | *III. Timeline* |
| | |
| | Feb. : Add NSDL Collection Records into the Registry |
| | March - July: Development activities |
| | Aug - September: Assess issues in developing to use a service registry, produce final report |
| | |
| | *IV. Resources* |
| | |
| | 4 months of 1 FTE developer |
| | |
| | *V. Outcomes* |
| | |
| | # Report on activity findings (includes recommendations on future registry activities and support) |
| | # Published article based on report |
Home