[Updated: Oct-2024]
This is the blog for Data-Centric Engineering, an open-access journal published by Cambridge University Press and supported by the Lloyd’s Register Foundation. You can also find us on LinkedIn.
The DCE blog is a channel for sharing informed opinions and perspectives relating to research and technology in data-centric engineering. Articles should explore the benefits and implications of data science when improving the reliability, safety, and efficiency engineered systems.
Suggested blogs:
- Translational [industry]
- Research [academic]
- Tutorial [including
codeexamples] - Article summaries [publications of DCE journal]
Guidelines and recommendations
![]()
Format
We seek to publish pieces between 500 words and 1500 words. If longer, we may consider publication in series, at the editor’s discretion. If a blog is based on a published article, the authors should provide a link to the DCE publication.
Style
The main goal is brevity and focus. Outside of academic and tutorial posts, language should be understood by the general public with interests in new technologies of engineering data-science. Technical terms and jargon should be defined when used, ideally avoided if the terminology does not explicitly contribute to the discussion. The author should deal directly with the matter at hand, avoiding long introductions. The text should stand in itself: whilst you can include references, the post should not heavily rely on external sources to be understood.
Evidence and referencing
There is no need for academic citation styles. Links are sufficient, which should offer access to published works that provide details or examples. It is always better to direct readers to open-access sources. The author can provide links in-text to the editorial team, who will add them to the final publication. Although the citation format is informal, authors should take care to appropriately acknowledge any sources and avoid plagiarism.
Visual resources
Visual resources (including charts, diagrams and graphs) can be useful to introduce and summarise content. They should be labelled appropriately and connected to the sources of primary or secondary data. The editorial team may add images to blog posts to facilitate reading. Preferably, the author has proper rights of use and access to specific images and seeks to have them included in the publication.
For tutorial and/or academic posts, one can display code,
def hello_world():
print("hello, world!")equations,
\[ \ddot{x}+\delta \dot{x}+\alpha x+\beta x^3 = f(t) \]
as well as graphs, etc. All the functionality of qaurto is available, see the documentation for details.
Editorial input
All posts will be assessed by the DCE editorial team before a decision is made about publication. Our communications editor may suggest changes to authors, including language, sources and structure. If the changes needed are major, we may suggest a different deadline or theme for their consideration. Corrections and updates to the blog are at the discretion of the DCE editorial team. Authors will be informed/consulted on any changes. All changes, including removal, will be made transparently.
Post-publication
The DCE team will encourage the author to promote the published article across their personal social media profiles and any associated institutional accounts - including universities, research groups and others. DCE may write additional material and create graphics or videos to promote the contribution. The blog post might be used across all DCE communication channels: the website, newsletter, and social media.
This is the blog for Data-Centric Engineering, an open-access journal published by Cambridge University Press and supported by the Lloyd’s Register Foundation. You can also find us on LinkedIn. Here are instructions for submitting an article to the journal.