Keywords[edit]

Bibliometrics, Natural Language Processing (NLP), Named-entity recognition (NER), Scholarly Communication, Information Retrieval, Semantic Parsing

Lookup of events by reference[edit]

As a scholar when i find a reference like 'In: proceedings of .... " i want to search for the conference referenced by cut&paste of the proceedings title of the conference into a search engine. The engine should find the presumably existing and unique event. It then should get all the relevant details of the event and present them". Especially i am interested in the quality and trustworthyness of the data (the confidence the system has in the results).

Scenario[edit]

The following scenario would be an acceptance criterion for the fullfilling the scholar's needs in this usecase:

Situation[edit]

During an internet search on software engineering topics a scholar finds the text:

• https://archive.org/stream/springer_10.1007-3-540-49205-4/10.1007-3-540-49205-4_djvu.txt

With a reference:

[Allo96] I. Alloui and F. Oquendo. “PEACE4-: a multi-agent system for computer- supported 
cooperative work in Software Process Centered Environments.” In Proceedings of 
8th International Conference on Software Engineering and Knowledge 
Engineering (SEKE’96), Nevada, June 1996. 

Action[edit]

Now the scholar would like to learn more about the SEKE'96 conference. Given his past bad experiences with searching just for the acronym "SEKE'96" he hopes that more information is better and uses cut&paste to search for

Proceedings of 
8th International Conference on Software Engineering and Knowledge 
Engineering (SEKE’96), Nevada, June 1996

E.g at DBLP. See https://github.com/WolfgangFahl/ProceedingsTitleParser/issues/25

This approach leads to:

with the frustrating result "no matches".

Expected Result[edit]

• https://dblp.org/db/conf/seke/seke1996.html
• https://dblp.org/db/conf/seke/index

<dblp>
<proceedings key="conf/seke/1996" mdate="2014-12-04">
<title>
The 8th International Conference on Software Engineering and Knowledge Engineering, SEKE '96, Lake Tahoe, Nevada, USA, June 10-12, 1996
</title>
<booktitle>SEKE</booktitle>
<publisher>Knowledge Systems Institute</publisher>
<year>1996</year>
<isbn>0-9641699-3-2</isbn>
<url>db/conf/seke/seke1996.html</url>
</proceedings>
</dblp>

WikiData[edit]

As of 2020-06 only 93 entities of type Q74258130 scientific conference Series are available in WikiData.

Example WikiData SPAQRL Query: Conference Series[edit]

# WF 2020-06-07

SELECT ?item ?itemLabel 
WHERE 
{
  #  scientific conference series (Q47258130) 
  ?item wdt:P31 wd:Q47258130.
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}

try it!

Wikidata Proceedings instances[edit]

As of 2020-06 some 1200 proceedings in Wikidata are instances of

• Q1143604 - proceedings

and can be e.g. directly queried with: wikidata vizquery for proceedings

Wikidata as a source of proceeding titles[edit]

As of 2020-06, some 35.7 million scholary article entities are available via Wikidata. We have used the https://tools.wmflabs.org/wdumps/ tool to create an RDF dump of the data of these entities https://tools.wmflabs.org/wdumps/dump/420.

In the next step, we filtered English proceeding titles by using the Unix command-line tool "grep" with the search expression "proceedings of". The resulting text file contained one subject-predicate-object triple per proceedings volume, e.g., for the above example:

<http://www.wikidata.org/entity/Q69349965> <http://www.w3.org/2000/01/rdf-schema#label> "Computer-assisted modeling of receptor-ligand interaction. Theoretical aspects and applications to drug design. Proceedings of the 1988 OHOLO Conference. Eilat, Israel, April 24-28, 1988"@en .

In total, we obtained a sample of 16,000 proceedings titles this way.

The analysis of the proceeding titles was facilitated by using a Python script with a simple first parsing approach. The first parsing approach separated each title into tokens by using whitespace as a delimiter. Then a dictionary in human readable "yaml" format was created that contained lookup tables for common words which were found in the proceeding titles. The dictionary was grouped into 14 dictionary elements.

Dictionary elements[edit]

This table shows the dictionary elements that already cover 65% of the most used words in proceedings titles. The assumption is that the 35% "long tail" will mostly have acronym and field information while adding more countries, city, enum and the like will not have much of an effect any more on the coverage. Please that the differenciation between upper and lowercase is on purpose.

Example lookup of tokens[edit]

The dateRange syntax element was added later when we switched to an improved parser and is not based on a dictionary.

Event Series and the enum element[edit]

Quite a few events are part of a series of events. E.g.

Catecholamines in the cardiovascular system. Proceedings of the 23rd Symposium on Catecholamines in the Cardiovascular System. Tokyo, Japan. November 30, 2002

http://www.wikidata.org/entity/Q73578487 is the title of the 23rd event in a series. The wikidata sample has two entries of proceedings for the corresponding series which can be found with the unix "grep" tool like this:

grep "Symposium on Catecholamines in the Cardiovascular System" proceedings.txt  | grep "@en"
<http://www.wikidata.org/entity/Q74122319> <http://www.w3.org/2000/01/rdf-schema#label> "Proceedings of the 22nd Symposium on Catecholamines in the Cardiovascular System. Tokyo, Japan, October 28, 2000"@en .
<http://www.wikidata.org/entity/Q73578487> <http://www.w3.org/2000/01/rdf-schema#label> "Catecholamines in the cardiovascular system. Proceedings of the 23rd Symposium on Catecholamines in the Cardiovascular System. Tokyo, Japan. November 30, 2002"@en .

Since the enumerating (ordinal) of events can be specified in a few different ways e.g.

• Arabic: 1,2,3, ..., 23
• Roman: I, II, III, ..., XXIII
• Ordinal words: First, Second, Third, ..., Twenty-third

it is necessary to find the numeric value of the enumeration. To simplify this the dictionary contains the "value" for each enumerarion e.g.:

grep -B 2 "value: 23" dictionary.yaml 
'23.':
  type: enum
  value: 23
--
23rd:
  type: enum
  value: 23
--
Twenty-third:
  type: enum
  value: 23
--
XXIII.:
  type: enum
  value: 23

Feasibility check of dictionary use[edit]

With a python unit test it was checked how many proceedings title in the 16.000 Wikidata samples could be successfully parsed using the dictionary. The most often used words were entered into the dictionary and the type of the word determined. In total 261,899 tokens where parsed of which 170,604 (65%) could be looked up in a dictionary with 694 entries.

Using a Grammar based parser[edit]

Then next step in improving the parser is applying a Proceedings titles specific grammar. The list of dictionary elements found with the with the dictionary approach has shown that it might be feasible to parse the proceedings titles by assuming that each dictionary element can be described as a grammar element. Also there are elements like daterange which were found but not handled by the dictionary approach yet. E.g. to analyze time metadata like "25-28 August, 2010" the three grammar elements

1. daterange
2. month
3. year

with the expected parse tree to be:

would be used. In this step we can now add extra flexibility. We now have the option to derive the grammar element from a dictionary element or specify a rule based approach. E.g. for the dictionary element "year" it seems awkward to have a dictionary of all years that might be valid. It is much simpler to specify a grammar rule that specifies a year to be a 4 digit number. For the month both options seem to be equally valid - there are only 12 different options in theory. The dictionary approach has the advantage that it would be easier to e.g. internationalize the paser because the parser itself could be fixed but use different dictionaries for different languages. For the daterange the grammar approach is definitly to be preferred because otherwise the dictionary would have to have a entries for a few hundred valid combination of dates that do not really add value to the dictionary.

We used the pyparsing-library for the grammar approach. Pyparsing describes the grammar in a human readable way right in the source code. Unfortunately there seems to be no tool to convert the source code to BNF form so the source code is shown verbatim below:

proc=Keyword("Proceedings") | Keyword("proceedings")
        descWord=~proc + Word(alphas+nums+"™æéç)>/'&—‐") # watch the utf-8 dash! 
        initials="("+OneOrMore(Word(alphas)+".")+")"
        desc=Optional("[")+OneOrMore(descWord|initials)+oneOf(". ? : ( , ; -")
        enumGroup=dictionary.getGroup("enum")
        scopeGroup=dictionary.getGroup("scope")
        eventGroup=dictionary.getGroup("event")
        freqGroup=dictionary.getGroup("frequency")
        yearGroup=dictionary.getGroup("year")
        cityGroup=dictionary.getGroup("city")
        provinceGroup=dictionary.getGroup("province")
        countryGroup=dictionary.getGroup("country")
        eventClause=dictionary.getClause("event")
        monthGroup=dictionary.getGroup("month")
        extractGroup=dictionary.getGroup("extract")
        dateRangeGroup=Group(Optional(Word(nums)+Optional("-"+Word(nums))))("daterange")
        prefixGroup=Group(ZeroOrMore(~oneOf(eventClause)+Word(alphas+nums)))("prefix")
        topicGroup=Group(ZeroOrMore(~oneOf("held on")+Word(alphas+nums+"-")))("topic")
        part="Part"+oneOf("A B C 1 2 3 4 I II III IV")+"."
        whereAndWhen=Optional(oneOf([".",",","held on"])+dateRangeGroup+monthGroup+dateRangeGroup \
                              +Optional(oneOf(","))+yearGroup \
                              +Optional(oneOf(","))+cityGroup \
                              +Optional(oneOf(","))+provinceGroup \
                              +Optional(oneOf(","))+countryGroup \
                              +Group(Optional(Word(alphas)))("location"))
        self.grammar=Group(ZeroOrMore(desc))("description") \
            +Optional(part) \
            +Optional(oneOf("[ Conference Scientific")) \
            +extractGroup+Optional(oneOf("the The"))+Optional("Official") \
            +proc+"of"+Optional(oneOf("the a an")) \
            +yearGroup \
            +enumGroup \
            +freqGroup \
            +scopeGroup \
            +prefixGroup \
            +Optional(oneOf("Scientific Consensus"))+eventGroup \
            +Optional(oneOf("on of in :")) \
            +topicGroup \
            +Optional(oneOf("] )")) \
            +whereAndWhen

dictionary.getGroup is the function which converts a list of dictionary elements with a given type to a list of valid grammar tokens allowing to use a dictionary type directly as a grammar element. This makes the grammar much more readable and flexible than specifying the list of possible token elements in the grammar itself.

match results[edit]

For the three different test sets of proceedings titles the parsers matching capability is over 97% in all cases. In a test driven development cycle for each special case found another test example was added. Special cases found where e.g. the use of UTF-8 chars like "‐" which looks like a dash but isn't or accents like "æéç" which are not in the default character set of the pyparsing library.

The test examples for the grammar above where are shown below in the corresponding python unit-test:

  def testExamples(self):
        ''' test specific examples for parsing success '''
        titlelines=[
            "Computer-assisted modeling of receptor-ligand interaction. Theoretical aspects and applications to drug design. Proceedings of the 1988 OHOLO Conference. Eilat, Israel, April 24-28, 1988",
            "Advances in chronic kidney disease 2009. Proceedings of the 11th International Conference on Dialysis. January 28-30, 2009. Las Vegas, Nevada, USA",
            "Nutrition in Clinical Management of HIV-Infected Adolescents (>14 y old) and Adults including Pregnant and Lactating Women: What Do We Know, What Can We Do, and Where Do We Go from Here? Proceedings of a conference held in Washington, DC, July 26-28",
            "Abstracts of the Official Proceedings of the 11th Annual Meeting of the American Society of Breast Surgeons. April 28-May 2, 2010. Las Vegas, Nevada, USA",
            "Old and New Dopamine Agonists in Parkinson's Disease: a Reappraisal. Proceedings of the LIMPE Seminar, 26-28 February, Pisa, Italy, 2009",
            "The Proceedings of the 97th Tohoku Regional Meeting of the Japanese Society of Neurology",
            "Subchondral Pathology: Proceedings of the International Consensus Meeting on Cartilage Repair of the Ankle",
            "Scientific Proceedings of the Twenty-seventh Annual Meeting of the American Association of Pathologists and Bacteriologists",
            "Bulletins et Mémoires de la Société Française d'Ophtalmologie: Proceedings of 1980 Congress",
            "British Pædiatric Association: Proceedings of the First Annual General Meeting",
            "Advances in Medical Computing (Proceedings of the 3rd International Symposium on Computers in Medicine)",
            "Red Drum Aquaculture, Proceedings of a Symposium on the Culture of Red Drum and Other Warm Water Fishes",
            "A summary of the Proceedings of the Twelfth International Symposium on the Neurobiology and Neuroendocrinology of Aging, Bregenz, Austria July 27-August 1, 2014.",
            "[Update on vaccine research. Proceedings of the 15th annual conference on vaccine research organized by the National Foundation for Infectious Diseases].",
            "Very broad Markush claims; a solution or a problem? Proceedings of a round-table discussion held on August 29, 1990.",
            "Abstracts From the Proceedings of the 2015 Annual Meeting of the Clerkship Directors of Internal Medicine (CDIM).",
            "Christo Deltshev & Pavel Stoev (eds) (2006): European Arachnology 2005, Acta zoologica bulgaria, Suppl. No. 1; Proceedings of the 22nd European Colloquium of Arachnology, Blagoevgrad, Bulgaria, 1-6 August 2005",
            "(L.) Bricault and (M.J.) Versluys Eds Power, Politics, and the Cults of Isis: Proceedings of the Vth International Conference of Isis Studies (Religions in the Graeco-Roman World 180). Leiden: Brill, 2014. Pp. xvii + 364. €139/$180. 9789004277182",
            "Kunaitupii: Coming Together on Native Sacred Sites—Their Sacredness, Conservation and Interpretation. Brian O. K. Reeves and Margaret A. Kennedy, editors. Proceedings of the First Joint Meeting of the Archaeological Society of Alberta and the Monta",
            "Jan Apel and Kjel Knutsson: Skilled Production and Social Reproduction. Aspects of Traditional Stone‐Tool Technologies. Proceedings of a Symposium in Uppsala, August 20–24, 2003",
            "Developing ambient intelligence - proceedings of the first international conference on ambient intelligence developments."
            #"Sea Lice 2003 - Proceedings of the sixth international conference on sea lice biology and control"
            ]
        parser=self.getParser()
        tc=Counter()
        for line in titlelines:
            self.tryParse(line, parser, tc)
        self.assertEqual(tc["success"],len(titlelines))

Using a Graph of Terms[edit]

Building on the dictionary approach the next step was to create a graph of the terms found while parsing. Each node in the graph consist of a term found in a proceedings title. A term can consist of one or multiple words and is either a syntactic element like "of the" or a term containing relevant typed meta-data information like "Symposium" of type "event. Terms may consist of multiple words so "San Francisco" is a term consisting of two words of type "city".

Example Graphs of Terms[edit]

Input taken from dblp xml[edit]

<title>Proceedings of the 27th International Symposium on Graph Drawing and Network Visualization (GD 2019).</title>
<title>Proceedings of the 25th International Symposium on Graph Drawing and Network Visualization (GD 2017).</title>
<title>Proceedings of the 24th International Symposium on Graph Drawing and Network Visualization (GD 2016).</title>
<title>Proceedings of the 26th International Symposium on Graph Drawing and Network Visualization (GD 2018).</title>

Graphical representation of the graph of terms[edit]

Input taken from WikiData[edit]

grep "International Symposium on Avian Influenza" proceedings.txt 
<http://www.wikidata.org/entity/Q79344682> <http://www.w3.org/2000/01/rdf-schema#label> "Proceedings of the 5th International Symposium on Avian Influenza. Athens, Georgia, USA. April 14-17, 2002"@en .
<http://www.wikidata.org/entity/Q86564245> <http://www.w3.org/2000/01/rdf-schema#label> "Proceedings of the 8th International Symposium on Avian Influenza, April 1-4, 2012, London, Great Britain"@en .
<http://www.wikidata.org/entity/Q80467391> <http://www.w3.org/2000/01/rdf-schema#label> "Proceedings of the Sixth International Symposium on Avian Influenza. April 3-6, 2006. Cambridge, United Kingdom"@en .
<http://www.wikidata.org/entity/Q84580794> <http://www.w3.org/2000/01/rdf-schema#label> "Proceedings of the Seventh International Symposium on Avian Influenza. April 5-8, 2009. Atlanta. Georgia. USA"@en

Please note the slight differences in wording, order and usage of syntactical elements. The 5th Symposium as the date at the end of it's title, while the others have the location at the end. The 5th and 8th use an arabic ordinal but not the 7th instead "Seventh" is used for the enumeration. Another difference is: "Great Britain" (country) - "London" (city) for the location but "United Kindom" as a country for the city "Cambridge" which is in fact in the same country. For the location "Georgia, USA," is used in the title of the 5th Symposium separating city and province by a comma but "Atlanta. Georgia." using a dot as a separator for the title of the 7th Symposium held in a location close by.

For a human these slight differences might be no big issue - for a systematic computerized approach it makes more sense to standardize the format of the metadata retrieved to ease the access to and analysis of such data.

Histogram analysis[edit]

The word count distribution for the proceeding titles of the four sources first looked like this:

The outliers in these distributions have been further analyzed assuming artifacts might be the reason.

• For ceur-ws we found that empty newlines had been created during the filtering from html to text.
• After improving the filter to retrieve more titles the ceur-ws histogramm didn't have the outlier at word count "1" any more - but the distribution looked suspicously wide:

reanalysis[edit]

SQL-Query[edit]

select source,title from event 
where title like '%Proceedings of%'
and source in ('wikidata')

Diagrams[edit]

grobid[edit]

see also GROBID 1

• https://github.com/kermitt2/grobid
• https://github.com/kermitt2/grobid-client-python

Example[edit]

Tested on https://grobid.bitplan.com Service to call: Process Citation

Input:

Proceedings of the International Workshop on Algorithms & Theories for the Analysis of Event Data 2020 (ATAED 2020),virtual workshop, June 24, 2020

Output:

<biblStruct >
    <monogr>
        <title level="m">Proceedings of the International Workshop on Algorithms &amp; Theories for the Analysis of Event Data 2020 (ATAED 2020),virtual workshop</title>
        <meeting>the International Workshop on Algorithms &amp; Theories for the Analysis of Event Data 2020 (ATAED 2020),virtual workshop</meeting>
        <imprint>
            <date type="published" when="2020-06-24" />
        </imprint>
    </monogr>
</biblStruct>

Falcon[edit]

• https://labs.tib.eu/falcon/ see 1

Example[edit]

Input:

Proceedings of the 27th International Symposium on Graph Drawing and Network Visualization (GD 2019)

Output:

{

    "entities": [
        [
            "http://dbpedia.org/resource/International_Symposium_on_Graph_Drawing",
            "27th International Symposium on Graph Drawing"
        ],
        [
            "http://dbpedia.org/resource/Sum_activity_of_peripheral_deiodinases",
            "(GD"
        ],
        [
            "http://dbpedia.org/resource/Visualization",
            "Network Visualization  2019)"
        ]
    ],
    "relations": [
        [
            "http://dbpedia.org/ontology/review",
            "proceedings"
        ]
    ]

}

Libraries Used[edit]

• https://github.com/pyparsing/pyparsing
• https://pypi.org/project/pywikibot/
• https://pypi.org/project/py-3rdparty-mediawiki/
• https://pypi.org/project/Flask/
• https://pypi.org/project/flask_accept/
• https://pypi.org/project/PyYAML/
• https://pypi.org/project/num2words/
• https://pypi.org/project/beautifulsoup4
• ...

Scholarly Search engine Trials[edit]

CiteSeer[edit]

ATAED 2020

• https://citeseerx.ist.psu.edu/search?q=Proceedings+of+the+International+Workshop+on+Algorithms+%26+Theories+for+the+Analysis+of+Event+Data+2020+%28ATAED+2020%29%2Cvirtual+workshop%2C+June+24%2C+2020&submit.x=0&submit.y=0&sort=rlv&t=doc gives 54.74 results as of 2020-07-03.

RefSeek[edit]

BIR 2019

• https://www.refseek.com/search?q=BIR+2019#gsc.tab=0&gsc.q=BIR%202019&gsc.page=1#

DBLP[edit]

For DBLP search test see https://github.com/WolfgangFahl/ProceedingsTitleParser/issues/25

WOS[edit]