From e2b2dd1f1ac9e94144399698f8684a0cb91ba3cb Mon Sep 17 00:00:00 2001
From: laijasmine <jasminelai@nceas.ucsb.edu>
Date: Tue, 7 Sep 2021 13:16:16 -0700
Subject: [PATCH] address #235

---
 workflows/edit_eml/set_physical.Rmd | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/workflows/edit_eml/set_physical.Rmd b/workflows/edit_eml/set_physical.Rmd
index 37bab61e..6de3d3e2 100644
--- a/workflows/edit_eml/set_physical.Rmd
+++ b/workflows/edit_eml/set_physical.Rmd
@@ -2,6 +2,10 @@
 
 To set the `physical` aspects of a data object, use the following commands to build a `physical` object from a data `PID` that exists in your package. **Remember to <a href = 'https://nceas.github.io/datateam-training/reference/set-dataone-nodes.html' target='_blank'>set the member node</a> to test.arcticdata.io!**
 
+```{block, type = "note"}
+The word ‘physical’ derives from database systems, which distinguish the ‘logical’ model (e.g., what attributes are in a table, etc) from the physical model (how the data are written to a physical hard disk (basically, the serialization). so,  we grouped metadata about the file (eg. dataformat, file size, file name) as written to disk in physical.
+```
+
 ```{r, eval = FALSE}
 physical <- arcticdatautils::pid_to_eml_physical(mn, pkg$data[[i]])
 ```