I felt that there hadn’t been any writing on this aspect of our envisaged architecture yet, so here’s a start at filling this particular gap:
- a typical source of local information
Let’s assume that some hunter-gathering has taken place, perhaps from a venue like this (right). Or alternatively, from a typical web-based resource. These items might need to be placed (virtually-speaking) in some some of holding pen, while an alert is sent about new arrivals. Whom might an alert go to? The straightforward institutional answer is ‘to the in-box of the local directory co-ordinator’ (who by the time that all this comes to pass will have evolved their role from collator to sifter and mentor…). But could we think more broadly than this – a sort of organisational equivalent of layering a folksonomy over and around a taxonomy? – so that while core labelling could be done institutionally, communities (individuals, schools, voluntary organisations (with their expert/specific focus), and practitioners could – perhaps over time and not all as soon as a potential resource is spotted (and only then) – add in their insights on what the resource could support?
We’d certainly want to enable tagging by resource-users, at the point of use, across at the right-hand side of our architecture. (ALISS Architecture outline – thanks to Fronds Reunited)
This action might take place either within or linked to applications that have been developed more or les independently, on the basis of taking a feed from the database in the middle, so arranging the transmission of data additions back to the central database will need to be considered.
These are just first thoughts…
