Just like Ploppit, Plukkit is shaping up to be an API framework between the User GUI and the backend. It may be interposed between the client and Dspace (for data, media, etc.) as well as between the client and G
eoserver (for maps). We should experiment with the new (1.5) Lightweight Network Interface being put together at MIT by the Dspace team there (since I am teaching there this semester, I should go meet them!). Another model for the geospatial component of our repository may be the work that ERDAS (Leika) is doing with Leika Titan. Maybe there's something to be learnt there and possibly some open source code that we can coopt for our Ploppit and Plukkit GUIs. Worth investigating...
eoserver (for maps). We should experiment with the new (1.5) Lightweight Network Interface being put together at MIT by the Dspace team there (since I am teaching there this semester, I should go meet them!). Another model for the geospatial component of our repository may be the work that ERDAS (Leika) is doing with Leika Titan. Maybe there's something to be learnt there and possibly some open source code that we can coopt for our Ploppit and Plukkit GUIs. Worth investigating...
No comments:
Post a Comment