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

Implementing date-based sorting for call numbers in the browse lists #1366

Closed

Conversation

jrgriffiniii
Copy link
Contributor

@jrgriffiniii jrgriffiniii commented Sep 14, 2018

Resolves #1341

@jrgriffiniii jrgriffiniii changed the title Implementing date-based sorting for call numbers in the browse lists [WIP] Implementing date-based sorting for call numbers in the browse lists Sep 14, 2018
@jrgriffiniii
Copy link
Contributor Author

This should have extended test coverage and better code documentation.

@tampakis
Copy link
Contributor

@jrgriffiniii would you consider adding this functionality to the lcsort gem? https://github.com/pulibrary/lcsort

@jrgriffiniii
Copy link
Contributor Author

@tampakis I'll proceed by working to resolve this on pulibrary/lcsort#14

@coveralls
Copy link

coveralls commented Sep 14, 2018

Coverage Status

Coverage increased (+0.03%) to 96.698% when pulling 590f54e on issues-1341-jrgriffiniii-lc-call-number-sort into 81deec1 on master.

@jrgriffiniii jrgriffiniii force-pushed the issues-1341-jrgriffiniii-lc-call-number-sort branch from 29c4407 to 590f54e Compare September 14, 2018 13:37
@jrgriffiniii jrgriffiniii changed the title [WIP] Implementing date-based sorting for call numbers in the browse lists Implementing date-based sorting for call numbers in the browse lists Sep 14, 2018
@jrgriffiniii
Copy link
Contributor Author

Closed in response to pulibrary/lcsort#15 and #1367

@christinach christinach deleted the issues-1341-jrgriffiniii-lc-call-number-sort branch November 30, 2020 14:27
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

Successfully merging this pull request may close these issues.

3 participants