Wikidata:Property proposal/DBLP journal ID
DBLP journal ID
editOriginally proposed at Wikidata:Property proposal/Creative work
Description | identifier of computer science conference in the DBLP database |
---|---|
Data type | External identifier |
Domain | academic journal (Q737498) |
Allowed values | string |
Example 1 | Theory of Computing (Q7782416) → toc |
Example 2 | Journal of the ACM (Q1709878) → jacm |
Example 3 | ACM Transactions on Database Systems (Q4650734) → tods |
Source | dblp computer science bibliography (Q1224715) |
Planned use | no precise plan, but would be nice to add to existing entities |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://dblp.org/db/journals/$1/index.html |
See also | DBLP author ID (P2456) but this is for people identifiers, not scientific conference identifiers |
Motivation
editThis is the analogue of DBLP venue ID (P8926) but for journals. I alluded to it in the proposal for the latter Wikidata:Property proposal/DBLP conference ID, which was accepted, but just need support for this one too. Thanks! A3nm (talk) 22:01, 6 December 2020 (UTC)
Discussion
editThe Source MetaData WikiProject does not exist. Please correct the name. This looks like an external ID. Is there a reason to have it as string? ChristianKl ❪✉❫ 00:14, 7 December 2020 (UTC)
- Support --Skim (talk) 09:58, 7 December 2020 (UTC)
- @ChristianKl: no idea sorry, not experienced enough to know, what did you have in mind instead? That's what I requested when the analogous DBLP venue ID (P8926) was created. --A3nm (talk) 20:49, 7 December 2020 (UTC)
- DBLP venue ID (P8926) was created with the external-id datatype. I switched this also to external-id so it's the same as DBLP venue ID (P8926). ChristianKl ❪✉❫ 20:53, 7 December 2020 (UTC)
- Awesome, thanks! --A3nm (talk) 08:36, 9 December 2020 (UTC)
- DBLP venue ID (P8926) was created with the external-id datatype. I switched this also to external-id so it's the same as DBLP venue ID (P8926). ChristianKl ❪✉❫ 20:53, 7 December 2020 (UTC)
- Oppose This is not how DBLP implements its own identifiers. Read How to find the key of a person, a publication, or a stream? Conferences and journals in DBLP are part of a unified stream identifier (also referred to as a "Venue" in their search). DBLP venue ID (P8926) should be modified to be this generic streams ID including journals, etc. If we are proposing a new DBLP identifier it should be publication identifier property a la: journals/pvldb/Ley09 for DBLP: some lessons learned (Q56235152) and conf/sigmod/Ley92 for The term retrieval abstract machine (Q59622611), etc. It should be noted that DBLP only provides persistent URLs for persons and publications and not for streams, although they do have URL linkable records to such and they can be seen in their XML DB schema (but their website does not label such URLs as persistent even if the identifiers are in their published XML DB). Some examples for DBLP Venue/Stream could be journals/jacm for Journal of the ACM (Q1709878) and conf/asplos for International Conference on Architectural Support for Programming Languages and Operating Systems (Q6049586). Switching to using their Venue/Stream also allow us to cover all their Venues/Streams including things like series/lnee for Lecture Notes in Electrical Engineering (Q96331233) which would not be able to be linked if we use the current DBLP venue ID (P8926) and this proposal as is. We should not be trying to slice/dissect their identifiers even if they seem to have a hierarchy within them. 50.53.22.81 10:43, 9 December 2020 (UTC)
- @ChristianKl: thoughts on the above? Sj (talk) 19:49, 9 December 2020 (UTC)
The Source MetaData WikiProject does not exist. Please correct the name. ChristianKl ❪✉❫ 21:10, 9 December 2020 (UTC) The Source MetaData/More WikiProject does not exist. Please correct the name. maybe someone who knows more about journals can weigh in? ChristianKl ❪✉❫ 21:11, 9 December 2020 (UTC)
- @Florian.Reitz: can you advise, please? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:13, 9 December 2020 (UTC)
- Comment This proposal seems half-baked. The title/label is set to "DBLP journal ID", however the current description is "identifier of computer science conference in the DBLP database" and "See also" is "DBLP author ID (P2456) but this is for people identifiers, not scientific conference identifiers". Is this proposal about journals or conferences or something else. To that end, I modified DBLP venue ID (P8926) as per the opposition comment of 50.53.22.81 above; see Property talk:P8926#Corrections. I also made a proposal for DBLP publications; see Wikidata:Property proposal/DBLP publication ID. —Uzume (talk) 09:23, 10 December 2020 (UTC)
- Comment Disclosure: I work for the dblp project. I agree with the comments from 50.53.22.81 and Uzume that DBLP venue ID (P8926) should be a common property for conference, journal and series entities in dblp. For context, we refer to conferences/journals/series as 'streams' (of publications). Stable URLs for streams are provided at https://dblp.org/streams/$1 . Examples:
However, https://dblp.org/db/$1 also works. I propose to use a single property. We do not fully differentiate between the different types. It is true that most identifiers for journals start with 'journals/' and most identifiers for conferences start with 'conf/'. However, this is not guaranteed. There are (admittedly: only a few) cases where we assigned a "wrong" identifier to a stream. In other cases, we fitted unusual cases into our structure: E.g., we list arXiv (Q118398) as journals/corr but this is not a journal. In other cases, it can be difficult to distinguish journals/conferences and series. E.g, Electronic Notes in Theoretical Computer Science presents itself as a journal. However, after some user complaints we have decided to model it as a series series/entcs (there is also a deprecated journals/entcs which will become a redirect in the near future). I suspect that with people trying out new ways of publishing scientific papers, we will see more of those cases in the future. Having different properties for journals and conferences could prevent some errors. E.g. the correct DBLP identifier for the Very Large Data Bases Conference is conf/vldb. A user might wrongly set this property to journals/pvldb as all papers from VLDB are published in journals/pvldb. However, cases like this should be rare and easy to identify and fix if needed. Florian.Reitz (talk) 16:39, 10 December 2020 (UTC)
- @Florian.Reitz: I appreciate your response. I changed Property:P8926#P1630 (see 1320933884) to use the https://dblp.org/streams/$1 prefix instead of https://dblp.org/db/$1/ (notice the suffixed "/"). I am attempting to keep people from using DBLP venue ID (P8926) to refer to publication contents, e.g., https://dblp.org/db/conf/icdt is a valid reference to a stream/venue but https://dblp.org/db/conf/icdt/icdt2020 is not. I had attempted to prevent that with the trailing "/" but it works better with https://dblp.org/streams/$1 because then https://dblp.org/streams/conf/icdt is good and https://dblp.org/streams/conf/icdt/icdt2020 is properly broken (instead of my hack to try to break these references). FYI: Your team might want to update: How to use the dblp search API? so everything references "https" instead of "http" (perhaps it would be good to search all the FAQ and news content to update these sorts of URLs). Thank you. —Uzume (talk) 22:00, 10 December 2020 (UTC)
- Wow, looks I have triggered a much more insightful discussion than my original proposal. Thanks a lot for updating DBLP venue ID (P8926) and deflecting my misguided proposal. As far as I understand, the proposal is now obsolete and there is no need to create anything. --A3nm (talk) 23:28, 14 December 2020 (UTC)