A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Crossref: The Road Ahead - Q&A Report | |||||||||||||||||||||||
2 | ||||||||||||||||||||||||
3 | ||||||||||||||||||||||||
4 | # | Question | Answer(s) | Answer(s) | ||||||||||||||||||||
5 | 1 | hello! Anne, Paris (France) | Hi Anne! Welcome! Glad you’re here | |||||||||||||||||||||
6 | 2 | Will we get copies of these slides after? | Hi - yes we’ll share the slide deck afterwards | |||||||||||||||||||||
7 | 3 | Can you share the blog link please | https://www.crossref.org/blog/time-to-put-the-r-back-in-rd/ | |||||||||||||||||||||
8 | 4 | What downstream identifiers are you thinking of? | we’re going to allow identifiers to be tagged in citations, so software heritage IDs for software, URIs, PubMed IDs, wikidata IDs for now, but I expect that list will grow. | |||||||||||||||||||||
9 | 5 | Patricia hi hello will the metadata interest group come back at some point? I need a place to have opinions :) | Hi Mike! Yes I think we will. Patricia put it on hold while we catch up with implementing some of the feedback but we want to keep this open line of communication going - possibly a bunch of smaller more focused metadata taskforces. | yes what Ginny said - we defintely want your opinions! | ||||||||||||||||||||
10 | 6 | How do we determine if we have auto update for Orcid for our journals? | The researcher is invited to let Crossref automatically update their record (many do) - that’s just once and then it’s set up for all their publishers. All a publisher needs to do is include the ORCID iDs in the metadata records at Crossref | |||||||||||||||||||||
11 | 7 | What if the author has already added their work in ORCID? Is there deduplication? | There is indeed because is can be matched using the DOI | |||||||||||||||||||||
12 | 8 | Thank you Ginny - that's terrific to know | live answered | |||||||||||||||||||||
13 | 9 | Can we request user based auth for us as an existing member? This is something we've been hoping for. | Yes, we can set you up, Ben. You can simply contact us at support@crossref.org and let us know which email addresses need access on your account (include prefix/username with your request as well). | |||||||||||||||||||||
14 | 10 | Can organization move to the new authentication model? How | Yes, we can set you up, Debra. You can simply contact us at support@crossref.org and let us know which email addresses need access on your account (include prefix/username with your request as well). | |||||||||||||||||||||
15 | 11 | Do you have a link that has the list of enhancements to Similarity Check? | Not yet but there will be a blog post about it soon. | A previous blog post gave a taster https://www.crossref.org/blog/similarity-check-news-introducing-the-next-generation-ithenticate./ But, as Fabienne mentioned, we have an update to blog very soon | ||||||||||||||||||||
16 | 12 | What about Scholix et Scholexplorer ? | live answered | |||||||||||||||||||||
17 | 13 | thank you | ||||||||||||||||||||||
18 | 14 | Thanks Fabienne! | ||||||||||||||||||||||
19 | 15 | Can you share the slides from today plz? | Yes we will follow up with the slides, recording, and all these links we’ve shared | |||||||||||||||||||||
20 | 16 | Are you going to increase the Similarity Check performance? Now the checking takes about 10-15 minutes for average article. | live answered | |||||||||||||||||||||
21 | 17 | Thanks Issac | ||||||||||||||||||||||
22 | 18 | Singapore | Welcome. Thank you for joining us. | |||||||||||||||||||||
23 | 19 | Are new activities added to the roadmap as they come up or is there a period of time that is reflected on the roadmap? | Our aim is to put everything onto the roadmap regardless of timeframe. We'll give an indication of when things are queued up next or we're actively working on them. | |||||||||||||||||||||
24 | 20 | Are members allowed to share ideas directly through the Trello board? | The Trello board is for Crossref to communicate the ideas we've already discussed internally. If you have a suggestion you can get in touch with any Crossref staff member directly, or via support@crossref.org. We're always open to new ideas and feedback! | We also welcome your comments on the Community Forum https://community.crossref.org/ | ||||||||||||||||||||
25 | 21 | I learned today about DUO - Data Use Ontology - perhaps that would be applicable to the sharing of data via the API..? | Thanks for the suggestion. We're keen to make reuse and licensing as clear as possible. I haven't come across DUO before, but we'll use anything that's broadly adopted across the communities we serve. | |||||||||||||||||||||
26 | 22 | is crossref using elasticsearch? if yes can i have documentation on that? | Stay tuned, we'll be talking about our API and a switch to elasticsearch later on. | This is the talk (from Dominika) that you need Abdulraham! | ||||||||||||||||||||
27 | 23 | When will Metadata Mgr be in final version, as there’ve been bugs since early this year. As this is a critical function, greatly appreciate that a stable and robust version is available soon. | We'll be mentioning this later on. My colleague Sara recently put out a blog post about our plans for content registration, including the future of Metadata Manager at https://www.crossref.org/blog/next-steps-for-content-registration/ | Patrick is now explaining that we’ll deprecate Metadata Manager - it’s buggy as you say - and it’s not flexible to work with non-journal content. So we’re building an entirely new and much better, more flexible tool! | ||||||||||||||||||||
28 | 24 | First, I've missed first 40 minutes and I don't know if it's mentioned or not. My question is that, do you have any plans/roadmap to enable v2 of deposit API (which OJS plugin uses) to all publishers? We use in-house deposit/XML generation software works with current HTTP/XML API but it's lack of some features (especially related to error reporting, like we are unable to match failed record with errors, it just gives general error message which does not include related record identifier/etc). | Hello, there are no plans for the deposit API used by OJS to be available for all. If you are having issues with sending us your XML and or retrieving error logs and interpreting those then do send us an email at support@crossref.org and we will do our best to help with your queries. | |||||||||||||||||||||
29 | 25 | Could you elaborate a little bit about considerations towards resilience of the crossref/doi-system, risk management, fall back solutions, decentral systems? From a policy and technical standpoint. Thank you | live answered | We'll be talking about this in the current section, but you might also want to read through Geoffrey's comments about our adoption of POSI which helps guide the policy part https://www.crossref.org/blog/crossrefs-board-votes-to-adopt-the-principles-of-open-scholarly-infrastructure/ | ||||||||||||||||||||
30 | 26 | Great for collaboration with DOAJ. Is it mean that we could merge some update both DOI and DOAJ in the same time? | That is a great idea. I know that DOAJ recently started accepting Crossref XML so there is already less duplication for journals in both orgs. We don’t have plans to integrate Content Registration witht hem on the technical side yet but I will raise it. Thanks! | |||||||||||||||||||||
31 | 27 | Thank you, Ginny. | ||||||||||||||||||||||
32 | 28 | Hi! Are patents and policies (e.g. gov. regulations) included in the event data? Or is this planned? | Not yet, but it's certainly an option if we can find suitable sources. | As Panos said, we'll be assessing future new sources later this year. We're just at the start of that process. | Do you have any suitable services for patents and policies Johannes? Suggestions gratefully received! | |||||||||||||||||||
33 | 29 | Thanks Martyn! | ||||||||||||||||||||||
34 | 30 | when will metadata mgr be retired? We're not familiar with XML and are not sure how to submit via other methods. | live answered | |||||||||||||||||||||
35 | 31 | I've not signed on Similarity Check, so should I hold on till V2 is available? is that in Jun 2021? | version 2 should be available in July for new users, so I would suggest waiting until then. But, please do contact us and we can keep you up-to-date | |||||||||||||||||||||
36 | 32 | This is a question for iThenticate: I may have missed you mentioning it, apologies. Does iThenticate take into account preprints separately? Our editors often find high similarities that are primarily based on preprints upon closer inspection. Is it possible to have this optionally marked somehow? | live answered | |||||||||||||||||||||
37 | 33 | Can Crossref help in a journal to be included in Scopus/ SCI? | We don't support applications to these services, members need to handle them by themselves. | Not really! Scopus uses our metadata of course like many other search/discovery/analytics tools | ||||||||||||||||||||
38 | 34 | Follow up: How would you know what a "legitimate" preprint is? Through a list of preprint servers? | Yes, there is a list identified as preprint servers | |||||||||||||||||||||
39 | 35 | OK | ||||||||||||||||||||||
40 | ||||||||||||||||||||||||
41 | ||||||||||||||||||||||||
42 | ||||||||||||||||||||||||
43 | ||||||||||||||||||||||||
44 | ||||||||||||||||||||||||
45 | ||||||||||||||||||||||||
46 | ||||||||||||||||||||||||
47 | ||||||||||||||||||||||||
48 | ||||||||||||||||||||||||
49 | ||||||||||||||||||||||||
50 | ||||||||||||||||||||||||
51 | ||||||||||||||||||||||||
52 | ||||||||||||||||||||||||
53 | ||||||||||||||||||||||||
54 | ||||||||||||||||||||||||
55 | ||||||||||||||||||||||||
56 | ||||||||||||||||||||||||
57 | ||||||||||||||||||||||||
58 | ||||||||||||||||||||||||
59 | ||||||||||||||||||||||||
60 | ||||||||||||||||||||||||
61 | ||||||||||||||||||||||||
62 | ||||||||||||||||||||||||
63 | ||||||||||||||||||||||||
64 | ||||||||||||||||||||||||
65 | ||||||||||||||||||||||||
66 | ||||||||||||||||||||||||
67 | ||||||||||||||||||||||||
68 | ||||||||||||||||||||||||
69 | ||||||||||||||||||||||||
70 | ||||||||||||||||||||||||
71 | ||||||||||||||||||||||||
72 | ||||||||||||||||||||||||
73 | ||||||||||||||||||||||||
74 | ||||||||||||||||||||||||
75 | ||||||||||||||||||||||||
76 | ||||||||||||||||||||||||
77 | ||||||||||||||||||||||||
78 | ||||||||||||||||||||||||
79 | ||||||||||||||||||||||||
80 | ||||||||||||||||||||||||
81 | ||||||||||||||||||||||||
82 | ||||||||||||||||||||||||
83 | ||||||||||||||||||||||||
84 | ||||||||||||||||||||||||
85 | ||||||||||||||||||||||||
86 | ||||||||||||||||||||||||
87 | ||||||||||||||||||||||||
88 | ||||||||||||||||||||||||
89 | ||||||||||||||||||||||||
90 | ||||||||||||||||||||||||
91 | ||||||||||||||||||||||||
92 | ||||||||||||||||||||||||
93 | ||||||||||||||||||||||||
94 | ||||||||||||||||||||||||
95 | ||||||||||||||||||||||||
96 | ||||||||||||||||||||||||
97 | ||||||||||||||||||||||||
98 | ||||||||||||||||||||||||
99 | ||||||||||||||||||||||||
100 |