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

Date range handling #3

Open
ilovan opened this issue Jul 6, 2022 · 3 comments
Open

Date range handling #3

ilovan opened this issue Jul 6, 2022 · 3 comments

Comments

@ilovan
Copy link
Contributor

ilovan commented Jul 6, 2022

Add use case for date ranges: canonical MODS handling, as described at https://www.loc.gov/standards/mods/userguide/attributes.html#point

<originInfo>
<dateOther point="start">20011008</dateOther>
<dateOther point="end">20011027</dateOther>
</originInfo>```
@ilovan
Copy link
Contributor Author

ilovan commented Jul 6, 2022

https://www.loc.gov/standards/datetime/ (EDTF date standards)

@jefferya
Copy link
Contributor

jefferya commented Sep 1, 2022

I'm unsure what these two should look like with respect to EDTF:

There is an type start and no type end. The output, not sure if it is in proper EDTF (the one after the separator).

orlando:904c6768-01a5-47c9-a45e-fc89a4b492c4 ==> "1976-_workbench_separator_1976"

     <mods:dateOther type="original">1976-</mods:dateOther>
     <mods:dateOther type="start" encoding="iso8601">1976</mods:dateOther>

orlando:1dfee0f8-e4ce-452a-aeae-d83a5055de0c ==> "2002-_workbench_separator_2002"

        <mods:dateOther type="original">2002-</mods:dateOther>
        <mods:dateOther type="start" encoding="iso8601">2002</mods:dateOther>

@jefferya
Copy link
Contributor

jefferya commented Sep 1, 2022

jefferya pushed a commit that referenced this issue Sep 2, 2022
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

2 participants