search

PoseiDAT / schemas

The core schemas for the PoseiDAT data interchange formats
MIT License
1 stars 5 forks source link

Feature/fish type as string #33

Closed Qwerios closed 2 years ago

Qwerios commented 2 years ago

Managing fish types involves a lot of data which differs per fishing method, target ERS country, etc. Our reference list contains well over 3000 codes in a managed system. Turning them into a flat enum and continuous updates does not seem sensible.

The pattern for a specie code is still enforced this way while leaving the code selection to the client application and/or server

daanpape commented 2 years ago

I absolutely agree on this, it offers a more flexible way to define fish species.

Qwerios commented 2 years ago

Released as version v0.0.10

JensPauwels commented 2 years ago

@Qwerios As mentioned in the email it is also important to not forget to push this release to the npm repo. This ensures us that we can implement the new feature on our side.

Qwerios commented 2 years ago

@JensPauwels I beat your question by 15 seconds