Closed cornejotux closed 6 years ago
Sounds like a good idea. Although of course the newer version may no longer work with the code, so its a good example why versioning data sets is important.
I updated the whole section and everything worked.
On Mon, May 7, 2018 at 8:07 PM Matt Jones notifications@github.com wrote:
Sounds like a good idea. Although of course the newer version may no longer work with the code, so its a good example why versioning data sets is important.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NCEAS/sasap-training/issues/18#issuecomment-387270552, or mute the thread https://github.com/notifications/unsubscribe-auth/AJvVksrnYlFe_64fNxQsuvWV6VGc4BIiks5twQwNgaJpZM4T1ucz .
--
Jorge F. Cornejo-Donoso PhD Marine Science cornejotux@gmail.com http://www.jorgecornejo.net http://www.surforacle.net
Should we update the link to the most updated version of a data packages in KNB?
For example numeral 8.2 have a link to "https://knb.ecoinformatics.org/#view/urn:uuid:8809a404-f6e1-46a2-91c8-f094c3814b47" which indicates "NOTE: A newer version of this dataset exists"
Any thoughts?
I'm intending to do it on my sections, unless there is a reason to not doing it.