Closed zdavatz closed 11 months ago
Does not look to be very difficult to implement, but the resulting files will be VERY different, as the old Zur Rose Transfer.dat contained over 160'000 lines and we find only 90'000 lines in the new XLSX. Therefore I would suggest to open a separate Branch for this feature and ask the different consumers to see whether the resulting output files still serve their needs. Eg. for Elexis it could well be that some of medical cabinets are using articles not (yet) in firstbase.xlsx. And how can they report missing articles back? Via Medelexis?
I do not like the file name with a date stamp in it. I would prefer (may be via a link) to fetch https://www.firstbase.ch/sites/default/files/firstbase_healthcare_public_data-dump_latest.xlsx instead of https://www.firstbase.ch/sites/default/files/2023-09/firstbase_healthcare_public_data-dump%2C%2020230920.xlsx Any chance that firstbase could change this soon?
Removed Ruby 2.6 from supported versions. Is this problem for some downstream users?
https://www.ruby-lang.org/en/downloads/branches/ says about Ruby 2.6
Ruby 2.6
status: eol
release date: 2018-12-25
normal maintenance until: 2021-04-01
EOL: 2022-04-12
Build failed with this error message:
Fetching gem metadata from https://rubygems.org/........
ox-2.14.17 requires ruby version >= 2.7.0, which is incompatible with the
current version, 2.6.10
Error: The process '/opt/hostedtoolcache/Ruby/2.6.10/x64/bin/bundle' failed with exit code 5
Option name will be "-b" or "--firstbase" withan help text of " -b, --firstbase build all NONPHARMA articles on firstbase"
you can remove Ruby 2.6.0, no probelm.
oddb2xml
with the option--fb
should build all NONPHARMA products on firstbase.