Issue 18203

individual name embedded in path to attached resource

18203
Reporter: kylecopas
Assignee: bko
Type: Improvement
Summary: individual name embedded in path to attached resource
Priority: Critical
Resolution: Fixed
Status: Closed
Created: 2016-02-03 13:58:45.484
Updated: 2017-10-10 14:56:32.691
Resolved: 2017-10-10 14:56:32.674
        
Description: On this page, there are two PDF attachments:
http://www.gbif.org/newsroom/news/fitness-for-use-task-groups-announced

They both have 'kylecopas' embedded in the URLs. Seeing that both of these documents should persist, could we update them to more generic addresses?

Meanwhile, is there anything that can be done to make the default setting for creating paths to such researches more general and consistent?

THX!]]>
    


Author: rdmpage
Comment: Wouldn't it make sense to assign DOIs to these sort of documents so that they have stable, citable identifiers?
Created: 2016-02-03 21:17:13.746
Updated: 2016-02-03 21:17:13.746


Author: kylecopas
Created: 2016-02-04 10:44:34.572
Updated: 2016-02-04 10:44:34.572
        
We've talked about it. Current thinking is that many of our documents have a limited shelf life, and DOI suggests a commitment to permanence. We can (and do) manage and redirect URLs if they change.

The more general issue here is of greater concern to meā€”that attachments get placed in more logical and general directory.
    


Author: rdmpage
Comment: Sure, but I think we're missing an opportunity to make these things citable by the wider community. Plus it reinforces the message that DOIs are useful and can be used for all sorts of things. It's hard to anticipate the long term use of documents (imagine a sociologist of science wanting to study GBIF, these sort of things are a gold mine). Why not show the community the way and put DOIs on all public documents?
Created: 2016-02-04 11:08:49.532
Updated: 2016-02-04 11:08:49.532


Author: kylecopas
Comment: Let's get data DOIs and related guidance fully sorted first. We have no scoping of the cost and responsibilities associated with making the leap to 'all public documents', but it's likely to be extremely high on both counts.
Created: 2016-02-04 11:44:41.521
Updated: 2016-02-04 11:44:41.521