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.

Sign up for GitHub

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

Jump to bottom

surface @n vs @label #102

Open
bwbohl opened this issue Feb 7, 2017 · 2 comments
Open

surface @n vs @label #102

bwbohl opened this issue Feb 7, 2017 · 2 comments
Labels
Area: Documentation Type: feature request
Milestone
1.0.0

Comments

@bwbohl
Copy link
Member

bwbohl commented Feb 7, 2017

use @n for technical order and @Label for displayable page name e.g. "1v"
@bwbohl bwbohl added this to the labels, titles, lang milestone Feb 9, 2022
@bwbohl
Copy link
Member Author

bwbohl commented Mar 29, 2022

+1 to this although it's currently possible to use any character in@n using it as mere technical ordering mechanism and @label as page-name allows for consistency checks. Of course @n should. be used as fallback.

On a second thought I wonder if we should just use the IIIF-Manifest of a source and whatever page-name is designated there.

@krHERO krHERO removed this from the labels, titles, lang milestone Jul 4, 2024
@bwbohl bwbohl added this to the 1.0.0 milestone Sep 6, 2024
@bwbohl
Copy link
Member Author

bwbohl commented Sep 6, 2024

At least some documentation on how Edirom Online deals with those attributes is needed.

@bwbohl bwbohl mentioned this issue Oct 11, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: Documentation Type: feature request
Projects
Edirom Development
Status: Backlog
Milestone
1.0.0
Development

No branches or pull requests
2 participants
@bwbohl @krHERO