Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

accession numbers being eaten? #1

Open
jedahan opened this issue Jun 19, 2015 · 0 comments
Open

accession numbers being eaten? #1

jedahan opened this issue Jun 19, 2015 · 0 comments

Comments

@jedahan
Copy link
Member

jedahan commented Jun 19, 2015

according to https://twitter.com/mdammers/status/593830388000227328

http://scrapi.org/object/436657 is the test case

it looks like some fields are called accessionNumber, and they are a javascript number

`````` "accessionNumber":6.1038```

and some are strings

"accession":"50.135.4"

not sure if it should revert to being strings because i wonder if multiple . in automatic number conversions are disallowed. I would lean towards making it a string - hard to process but correct data is better than bad data, and most accession numbers are for identification purposes first, sorting second...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant