I queried dblp for "Breitenbücher".
Following entry came out:
@InProceedings{Hahn2018b,
author = {Michael Hahn and Uwe Breitenb{\"{u}}cher and Frank Leymann and Vladimir Yussupov},
booktitle = {On the Move to Meaningful Internet Systems. {OTM} 2018 Conferences - Confederated International Conferences: CoopIS, C{\&}TC, and {ODBASE} 2018, Valletta, Malta, October 22-26, 2018, Proceedings, Part {II}},
date = {2018},
title = {Transparent Execution of Data Transformations in Data-Aware Service Choreographies},
doi = {10.1007/978-3-030-02671-4\_7},
editor = {Herv{\'{e}} Panetto and Christophe Debruyne and Henderik A. Proper and Claudio Agostino Ardagna and Dumitru Roman and Robert Meersman},
pages = {117--137},
publisher = {Springer},
series = {Lecture Notes in Computer Science},
url = {https://doi.org/10.1007/978-3-030-02671-4_7},
volume = {11230},
bibsource = {dblp computer science bibliography, https://dblp.org},
biburl = {https://dblp.org/rec/conf/otm/0002BLY18.bib},
owner = {koppor11},
}Thus, I have the DOI 10.1007/978-3-030-02671-4\_7
When activating "Citation Relations", I get
Illegal character in path at index 76: https://api.semanticscholar.org/graph/v1/paper/DOI:10.1007/978-3-030-02671-4\_7/references?fields=title,authors,year,citationCount,referenceCount&limit=1000
Error while fetching citing Articles
java.lang.IllegalArgumentException: Illegal character in path at index 76: https://api.semanticscholar.org/graph/v1/paper/DOI:10.1007/978-3-030-02671-4\_7/citations?fields=title,authors,year,citationCount,referenceCount&limit=1000
I think, this needs to be fixed at the DOI parsing logic (or at semantic scholar?)
This issue is more about code reading and code understanding. The fix itself is probably 3 lines of code and 10 lines of test case.
I queried dblp for "Breitenbücher".
Following entry came out:
Thus, I have the DOI
10.1007/978-3-030-02671-4\_7When activating "Citation Relations", I get
I think, this needs to be fixed at the DOI parsing logic (or at semantic scholar?)
This issue is more about code reading and code understanding. The fix itself is probably 3 lines of code and 10 lines of test case.