The Presentation Layer
The Innovation Stack
Dr. Richard Fujimoto has presented the idea of an Innovation Stack to abstract how users innovate in science.
-
Applications
An application space for innovation
-
Presentation
Visualization, reporting, sharing, and dissemination of innovation and the innovation stack.
-
Data Processing
Numerical packages, algorithms, and knowledge that digest data to generate new knowledge.
-
Storage & Middleware
Infrastructure to organize & execute both codes & data.
-
Hardware & System Software
Computers, mobile devices, notebooks, etc. that drive innovation.
The Presentation Layer
The presentation layer of your research are any form of its public facing components. Peer reviewed journal articles on Science Direct, a downloaded PDF, and a print of the PDF all indicate different presentation layers for similar content. Presentation layers make content visible to your peers.
Technology has severely disrupted presenting content in the mainstream, but the materials science and many physical scienes are slow to adapt. Leveraging modern technology to publish research science content is disruptive. We will raise new concerns and overshadow old concerns.
Where are some examples of technology as a disruption?
Units of Work
In physics, units of work are defined in Joules. The velocity of software development is defined by units of work over a time interval with units analogous to . Units of work describe human capital invested into a project.
Projects, or large workflows, are build upon parallel and serial units of work. Units of work may:
- Produce Data
- Produce Software
- Perform Experiments
- Run-time Costs
- Publish/Share results
Every operation can be accounted for as a unit of work. Understanding the cost and repetitiveness of units of work can provide scientists with heuristics for knowing when and when not to pipeline.
In the class we will often compare convential and progressive units of work.
Units of Work in Research
There are units of work in empirical and computational research projects. Understanding Units of Work in methodologies and research tasks can only be understood by domain experts. It is expected that that domain itself will compact, streamline, and express units of work.
In this course, we can’t directly help you with streamlining research work.
Units of Work in Publishing
Publishing can be used for:
- Internal or personal use
- Sharing with a research team
- Dissemination to the public
Units of work in publishing can be assessed better than in research. Also, units of work in publishing are pieces of the units of work in research. Maximizing the value for a particular unit of work will enhance and exedite the research even if it is simply to migitate latency in research.
In this class, we will rigorously Units of Work for publication and learn to streamline our collaborations using the best software we can.
MIME
Every time your web browser requests a page, the web server sends “headers” before it sends the actual page markup. These headers are normally invisible, although there are web development tools that will make them visible if you’re interested. But the headers are important, because they tell your browser how to interpret the page markup that follows. The most important header is called Content-Type, and it looks like this:
Content-Type: text/html “text/html” is called the “content type” or “MIME type” of the page. This header is the only thing that determines what a particular resource truly is, and therefore how it should be rendered. Images have their own MIME types (image/jpeg for JPEG images, image/png for PNG images, and so on). JavaScript files have their own MIME type. CSS stylesheets have their own MIME type. Everything has its own MIME type. The web runs on MIME types.
API’s
Application Programmer Interfaces construct data for programs and cloud services to share data with other websites to operate on or visualize. API’s enable reusability.
Views
Views are templating engines that aggregate API data into a front facing web view. URL’s are not static anymore, they are resemble functions.
Minimizing Units of Work
Using API’s
Web views do not present ALL of the data requested by a webpage. A front-end designer has chosen the salient features to be displayed based on a structured API call. This view may be enough to illustrate the contents of a piece of information to incentivize access from another user.
Flickr as an Example
When an image is uploaded to Flickr, the raw data is stored and so are several thumbnailed versions of the image. The thumbnailed images would be presented in a view, but they allow you to access the raw data!
Dropbox as an Example
Dropbox has default settings to view excel files, but they do not provide the same interactivity. The view of the Excel file presents useful information in communicating the contents of the data.
Lab to the Cloud on a Dime
Centralization
Meandering across several disparate software services by introduce inefficiencies in sharing information. Centalizing research by-products and dicussion can drastically reduce the Units of Work in information sharing and publication. Similarly, centralization will make it easier to aggregate already published research results when a project is deemed ready for peer review
Sharability, Interactivity, and Discoverability
A digitally minded publication process can assist in sharing information with a smaller unit of work. Sharing public or private links can drastically reduce units of work. Similarly, by-products grow organically during the research process. Creating digital publications provides an opportunity to further nuture your information by interactively engaging in digital discussions.
If information is in your lab notebook ain’t no one gon’ be able to find it!
Digital information is readily discoverable by domain experts, colleagues, and search engines. We all want our work found and that is easier to do digitally.
A blog aware publication process can share several Units of Work in a single link if we do it right.
Content First, Style… Later
Traditional publication methods like Powerpoint, Latex, and Word give researchers complete agency in how the way to style their content for dissemination. Unfortunately, scientists are not designers therefore styling publications can be a pipeline to avoid.
Markdown supports this mindset because it provides limited syntax that can have style sheets appended to it after the content has been vetted.
Context is Crucial
In this course we will learn to present content FIRST. Styling content will become a reward later on down the road.