Anonymous

User:Martind/Document Log Discovery Platform: Difference between revisions

From London Hackspace Wiki
m
no edit summary
mNo edit summary
mNo edit summary
Line 9: Line 9:
* Finally, can we think of these functions as a layer on top of mere archives, and construct them as a physically separate service?
* Finally, can we think of these functions as a layer on top of mere archives, and construct them as a physically separate service?
** How would such a service integrate with layers below (archives) and above (editorial, exploration)?
** How would such a service integrate with layers below (archives) and above (editorial, exploration)?
Addressability is a first technical barrier:
* Being able to construct links between multiple representations of the same documents
** Across mirrors (same content, same addressing scheme, different location)
** Across types of archive browsers (some may have further annotations, all may have different addressing schemes, all will have different locations)
* Being able to identify existing references/annotations by detecting such links
** E.g. via Twitter/Google search


Note:
Note:
Line 137: Line 130:
=== Addressing Schemes for Archives ===
=== Addressing Schemes for Archives ===


* Need a shared addressing scheme that works across archives, archive browsers
Addressability is a first technical barrier:
** Based on permalinks?
* Being able to construct links between multiple representations of the same documents
** Definite goal: to place links. Ability to send reader to the source material
** Across mirrors (same content, same addressing scheme, different location)
** Optional goal: simple API. Ability to load source material by forming an address. (This places more requirements on the nature of the archive of the respective source material.)
** Across types of archive browsers (some may have further annotations, all may have different addressing schemes, all will have different locations)
* Alternatively: need a method of translating between different addressing schemes
* Being able to identify existing references/annotations by detecting such links
** Start with a review of link structures of a wide spectrum of archives
** E.g. via Twitter/Google search
* Should publish best practises for a good addressing scheme
 
** Document the structure of individual addressing schemes
Need a shared addressing scheme that works across archives, archive browsers
** Publish recommendations for addressing schemes, terminology used: common conventions
* Based on permalinks?
* ...
* Definite goal: to place links. Ability to send reader to the source material
* Optional goal: simple API. Ability to load source material by forming an address. (This places more requirements on the nature of the archive of the respective source material.)
 
Alternatively: need a method of translating between different addressing schemes
* Start with a review of link structures of a wide spectrum of archives
 
Should publish best practises for a good addressing scheme
* Document the structure of individual addressing schemes
* Publish recommendations for addressing schemes, terminology used: common conventions


Spacelog highlights:
Spacelog highlights: