Context Navigation

← Previous Ticket
Next Ticket →

#627 closed enhancement (fixed)

Trackback support

Reported by:	skaplun	Owned by:	pglauner
Priority:	minor	Milestone:
Component:	WebStyle	Version:
Keywords:	trackback referer ping http cool	Cc:

Description

It would be cool and easy to add support for the trackback specifications.

This can be implemented by creating a simple bfe_element to be added to default html detail of a record and html brief.

A webhanlder should be added to accept pings: say /record/1234/trackback.

Moreover a new tab can be added in the detailed record, containing the list of URLs pointing to this record.

Additionally we can have silent trackback by reading HTTP headers when user are visiting /record/1234 URLs, and extracting the refer.

Change History (11)

comment:1 Changed 20 months ago by simko

Milestone set to v1.1
Owner set to pglauner
Status changed from new to assigned

comment:2 Changed 20 months ago by skaplun

The above mentioned trackback specification link is dead :-(

Still it seems that it has been proposed (in 2005!) to become an Internet standard. Latest draft of the protocol is available here:

http://www.lifewiki.net/attachments/view/101/2.2

comment:3 Changed 20 months ago by simko

For example, see http://arxiv.org/help/trackback, http://arxiv.org/tb/recent.

comment:4 Changed 20 months ago by pglauner

After discussion with Sam

General

New module WebLinkBack supporting linkbacks in general: http://en.wikipedia.org/wiki/Linkback
Supporting trackbacks initially: http://arxiv.org/tb/recent

Requirements

Extension in the detailed record:

New tab or part of the citation tab, see Inspire
../linkbacks referring to tab

Linkback overview for all records:

Something similar to http://arxiv.org/tb/recent
Maybe: invenio-instance/linkbacks
See webstyle/lib/webinterface_layout.py to add this

Approval mechanism:

Avoiding spam
Approval button for owner in linkback tab
Daemon for approval: daily or instant notification of owner (configurable)
Saving status in DB: pending, approved, rejected

Logging:

Who did do what when: user id, linkback id, time

Database:

Central table: link, realURL, foreign key to id_bibrec, blob column for all ping properties (use dbquery.py/serialize...() and deserialize...()

Tests:

Unit
Regression

Auto discovery:

Adding trackback link to every record, not using RDF documents

Version 3, edited 20 months ago by pglauner (previous) (next) (diff)

comment:5 follow-up: ↓ 6 Changed 20 months ago by jcaffaro

Dunno if this has been discussed IRL nor if this is really useful (or feasible in a simple way) but why not also supporting the trackback in the other direction (i.e. by pinging the remote site), for eg. when:

a link is posted in a WebComment
an external resource is added to a WebBasket
a record containing a remote link is WebSubmitted

Taking into consideration that some resources would be restricted...

comment:6 in reply to: ↑ 5 Changed 20 months ago by pglauner

I thought about this, too. We will offer this feature in a later step as receiving pings has priority.

Replying to jcaffaro:

Dunno if this has been discussed IRL nor if this is really useful (or feasible in a simple way) but why not also supporting the trackback in the other direction (i.e. by pinging the remote site), for eg. when:

a link is posted in a WebComment
an external resource is added to a WebBasket
a record containing a remote link is WebSubmitted
Taking into consideration that some resources would be restricted...