-
Notifications
You must be signed in to change notification settings - Fork 2
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
Sort by Date / Timeline #215
Comments
How about the Publication Statement? As for the dates I need them to either be ISO format or at least easy to convert. I think it is best to use the @to @from @when attributes with ISO dates and then within the tag you can use any date you like, i.e. 4th or 5th century. Here is an example of the timeline More useful may be the date slider as seen here: Same needs as far as date formatting goes. |
@davidamichelson @dlschwartz |
And I think publication statement would be fine. Will it work okay for sorting purposes if some of the texts are tagged to specific dates such as: |
I do like the date slider thing. We'd also want there to be a box for date on the advanced search page. |
Yes, although I think the correct ISO encoding is |
Oh yes. Thank you for the reminder. |
Okay, I have added some dates to a handful of texts for testing: |
@wsalesky None of the texts are encoded with date info yet. Any ideas about where that should be? I'm assuming in the tltleStmt somewhere. I can pick a few files for testing on dev server as soon as we nail down where the date should be encoded.
One thing we should think through: some texts may have specific dates, but many of them will just have a century (4th, 5th, etc.). I know we can encode a date with a range, like from=300 and to=400 for 4th century. Should we just encode all of them with that range, even when we have specific dates that fall within that range? In other words, what makes it easier on your end?
As for the Timeline, I don't really know how that works. So just let me know if I need to so something there.
The text was updated successfully, but these errors were encountered: