In reply to
@natesjacobs @csarven @lesliekwchan @ewout @sciteai @CrossrefOrg (16/N) But while we are on the subject of obligations... It is by now a truism that persistence is more a social problem than a technical one.
In reply to
@natesjacobs @csarven @lesliekwchan @ewout @sciteai @CrossrefOrg (16/N) But while we are on the subject of obligations... It is by now a truism that persistence is more a social problem than a technical one.
In reply to
@natesjacobs @csarven @lesliekwchan @ewout @sciteai @CrossrefOrg (15/N) And we also have orgs that are made up of just one person (hint).
In reply to
@natesjacobs @csarven @lesliekwchan @ewout @sciteai @CrossrefOrg (14/N) And we also have orgs that are just crap at meeting their responsibilities.
In reply to
@natesjacobs @csarven @lesliekwchan @ewout @sciteai @CrossrefOrg (13/N) Clearly, identifier-dweebs are outliers in this case and would probably be more responsible than most orgs in meeting CR obligations.
In reply to
@natesjacobs @csarven @lesliekwchan @ewout @sciteai @CrossrefOrg (12/N) So we have focused on orgs because they are generally better equipped to take on the responsibilities associated with updating their pointers (DOIs) and metadata.