ReadStatTables.jl icon indicating copy to clipboard operation
ReadStatTables.jl copied to clipboard

Published 20 hours ago • verified publisher icon junyuan-chen

Roadmap for v0.3.x release

Open junyuan-chen opened this issue 2 years ago • 2 comments
trafficstars

The upcoming v0.2.3 release is very likely to be the last one in the v0.2.x series. Development will target toward the v0.3.0 release once v0.2.3 is out. The goal is to get close to a full coverage of the ReadStat API for complete functionality while maintaining the performance advantage over the related packages.

Update: The v0.3.0 was released without covering all features envisioned in the past. Implementation for the missing features may be gradually rolled out in future v0.3.x releases. This may happen very slowly unless there is popular demand.

Here is a list of changes that could happen for v0.3.x:

  • [x] Use MappedArray to lazily convert variables in date/time format back and forth between format-specific numerical values and Julia Date/DateTime. (#36)
  • [ ] Support user-specified missing values (.a, ..., .z and value ranges) while maintaining the ease of getting back to missing (possibly with StructArray and MappedArray).
  • [ ] Elements in LabeledArrays that do not have a value label should be returned as the original value without being converted to String.
  • [ ] Support READSTAT_TYPE_STRING_REF for very long strings in Stata.
  • [ ] Use the integer column fields in ReadStatColumns for the reference arrays of PooledArray.
  • [ ] Support read/write value labels from/to .sas7bcat files.
  • [x] Add an copycols option to writestat for converting the user-provided table to ReadStatTable{ReadStatColumn} before row iteration. This could make writing data files faster. (#36)
  • [ ] Support reading/writing data by chunk.
  • [ ] Reproduce the sample data used for testing, ideally with scripts executed on Stata/SAS/SPSS.
  • [x] Require Julia v1.6 and ReadStat_jll.jl v1.1.8. Check compatibility of dependencies.

junyuan-chen avatar Dec 23 '22 03:12 junyuan-chen

The current version is 0.3.2 so this one needs an update or maybe it can be closed

andreasnoack avatar Feb 20 '25 14:02 andreasnoack

@andreasnoack Thanks! I should modify the title to avoid confusion, as this issue now becomes a reminder for things that may be considered for future v0.3.x.

junyuan-chen avatar Feb 21 '25 01:02 junyuan-chen