Visualising literary heritage: A viable approach? The case of the Panpoëticon Batavûm (1772–1780)

Lieke van Deinsen; Timothy De Paepe

doi:10.1016/j.daach.2016.11.003

Visualising literary heritage: A viable approach? The case of the Panpoëticon Batavûm (1772–1780)

Lieke van Deinsen, Timothy De Paepe^*

^*Corresponding author for this work

Research output: Contribution to Journal › Article › Academic › peer-review

Original language	English
Pages (from-to)	49-58
Number of pages	10
Journal	Digital Applications in Archaeology and Cultural Heritage
Volume	4
DOIs	https://doi.org/10.1016/j.daach.2016.11.003
Publication status	Published - 1 Mar 2017
Externally published	Yes

Access to Document

10.1016/j.daach.2016.11.003

Handle.net

Persistent link

Cite this

@article{78995bb766f04d95a8b96bed44f4e51b,

title = "Visualising literary heritage: A viable approach? The case of the Panpo{\"e}ticon Batav{\^u}m (1772–1780)",

author = "{van Deinsen}, Lieke and {De Paepe}, Timothy",

year = "2017",

month = mar,

day = "1",

doi = "10.1016/j.daach.2016.11.003",

language = "English",

volume = "4",

pages = "49--58",

journal = "Digital Applications in Archaeology and Cultural Heritage",

issn = "2212-0548",

publisher = "Elsevier BV",

}

TY - JOUR

T1 - Visualising literary heritage

T2 - A viable approach? The case of the Panpoëticon Batavûm (1772–1780)

AU - van Deinsen, Lieke

AU - De Paepe, Timothy

PY - 2017/3/1

Y1 - 2017/3/1

UR - http://www.scopus.com/inward/record.url?scp=85008210819&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=85008210819&partnerID=8YFLogxK

U2 - 10.1016/j.daach.2016.11.003

DO - 10.1016/j.daach.2016.11.003

M3 - Article

AN - SCOPUS:85008210819

VL - 4

SP - 49

EP - 58

JO - Digital Applications in Archaeology and Cultural Heritage

JF - Digital Applications in Archaeology and Cultural Heritage

SN - 2212-0548

ER -

Visualising literary heritage: A viable approach? The case of the Panpoëticon Batavûm (1772–1780)

Access to Document

Handle.net

Other files and links

Cite this