Open machawk1 opened 4 months ago
This could be implemented as a details-on-demand query for the TimeMap endpoint for the URI-R currently being visited. That endpoint should be encoded somewhere (banner metadata?) to act as a basis for the subsequent query for the TM.
Other Link header-based attributes are already exposed to Reconstructive, e.g.,
URI-T exposed to reconstructive component in e859277, now just need to setup the query on expanding the reconstructive view. Follow-on steps would be to output the raw data to the DOM, clean the state into a workable data structure (e.g., JSON if the CDXJ endpoint is used, else we might think to just access the JSON-based TimeMap), then ultimately visualize this data.
More done on echoing the contents of the TM per the Ajax request in issue-839 branch but sometimes the ServiceWorker intercepts the request for http://localhost:2016/timemap/cdxj/memento.us/ to http://localhost:2016/memento/20130202100000/memento.us/timemap/cdxj/memento.us/
A la the Wayback Machine.