Wikidata:Property proposal/DBLP journal ID

DBLP journal ID edit

Originally proposed at Wikidata:Property proposal/Creative work

   Withdrawn
Descriptionidentifier of computer science conference in the DBLP database
Data typeExternal identifier
Domainacademic journal (Q737498)
Allowed valuesstring
Example 1Theory of Computing (Q7782416)toc
Example 2Journal of the ACM (Q1709878)jacm
Example 3ACM Transactions on Database Systems (Q4650734)tods
Sourcedblp computer science bibliography (Q1224715)
Planned useno precise plan, but would be nice to add to existing entities
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://dblp.org/db/journals/$1/index.html
See alsoDBLP author ID (P2456) but this is for people identifiers, not scientific conference identifiers


Motivation edit

This 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)[reply]

Discussion edit

The 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? ChristianKl00:14, 7 December 2020 (UTC)[reply]

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). ChristianKl20:53, 7 December 2020 (UTC)[reply]
Awesome, thanks! --A3nm (talk) 08:36, 9 December 2020 (UTC)[reply]

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? ChristianKl21:11, 9 December 2020 (UTC)[reply]

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)[reply]

@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)[reply]
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)[reply]