[R-Forge #2197] A a simple labels attribute like in the Hmisc package for variable descriptions #623

Activity

1. geponce commented on Aug 14, 2015

   

   geponce

   on Aug 14, 2015

   More actions

   I second this feature and in relation to this, some of the functionality at Morpho (http://bit.ly/1Tzc7Nj) looks interesting and very related to what Griffith mentions above, I guess.
2. jangorecki

   added this to the 1.12.4 milestone on Jan 29, 2019
3. jangorecki

   removed this from the 1.12.4 milestone on Jul 25, 2019
4. MichaelChirico commented on Sep 2, 2019

   

   MichaelChirico

   on Sep 2, 2019

   Member

   More actions

   I think this issue needs a use case MRE.

   If this were implemented, nicely written variable names (with spaces and special characters) could appear in tables and plots that are output straight to latex, without post-processing.

   This seems to be quite a deep request and probably better suited to an add-on package as it will likely require S3 or S4 methods for columns to auto-replace their names with their labels.

   without spending hours hand coding variable abbreviations to complicated variable names

   I'm not seeing why this is the case. In the example, there weren't "hours spend hand coding" (unless that was already done upstream and is anyway moot) -- we simply copy the labels attribute onto the data.table object -- either the object itself, or onto the columns individually.

   This is and has always been possible (though I agree quite poorly documented) in base R and hence data.table. So, barring a more specific example of the anticipated workflow/API, I vote to close

   👍React with 👍1Reacted by Jan Gorecki
5. iagogv3 commented on Apr 17, 2020

   

   iagogv3

   on Apr 17, 2020

   Contributor

   More actions

   Todays, beyond Hmisc other packages like haven, labelled or sjlabelled contribute to manage labels in the tidyverse package family.

   I am starting to learn data.table, but not having the posibility of managing labels could discourage me to go on with it. It may be the case of many other people, since variable labels and categorical variable value labels are very useful.

   Thank you anyway for the great package.

   👍React with 👍1Reacted by Jan Gorecki
6. jangorecki commented on Apr 17, 2020

   

   jangorecki

   on Apr 17, 2020

   Last edited by jangorecki

   Member

   More actions

   It is even more important because non-native encoding in column names cannot be reliably handled everywhere, and it seems that we will have to force users to change their column names in some cases. In such case labels could still carry required column names in any encoding.
   @iago-pssjd could you maybe link a manual page that describes usage of those in some of the mentioned packages?

   👍React with 👍2Reacted by iagogv3 and Michael Chirico
7. jangorecki

   added

   beginner-task

   on Apr 17, 2020
8. iagogv3 commented on Apr 17, 2020

   

   iagogv3

   on Apr 17, 2020

   Contributor

   More actions

   Yes, I link two pages for both labelled and sjlabelled, even when the second overlap the first a bit:

   • https://cran.r-project.org/web/packages/labelled/vignettes/intro_labelled.html

   • https://strengejacke.github.io/sjlabelled/articles/intro_sjlabelled.html

   Thank you!

   👍React with 👍1Reacted by Jan Gorecki
9. jangorecki commented on Apr 17, 2020

   

   jangorecki

   on Apr 17, 2020

   Last edited by jangorecki

   Member

   More actions

   I had a brief look at links and it seems to be much broader approach.
   AFAIU what we really need is just an extra attribute, that has to be retained/handled during common operations

   d = data.table(celsius = 20, fahrenheit = 68)
   setlabels = function(x, labels) {
     setattr(d, "labels", labels)
   }
   setlabels(d, labels = c("°C","°F"))

   and then handle that nicely in print.data.table, fwrite(yaml=TRUE)

   print(d)
   #        °C         °F  
   #   celsius fahrenheit
   #1:      20         68

   👍React with 👍2Reacted by iagogv3 and Sindri