You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the information about the name and location of an entry's publication and/or archive can be stored in Hayagriva. However, the archive and publisher fields do not store data in the same way.
Publisher
Information regarding an entry's publisher can be stored either as a name:
publisher: <string>
or as an object with separate keys for its name and location:
publisher:
name: <string>
location <string>
Archive
Yet archival information is stored in a flat structure:
archive: <string>
archive-location: <string>
Proposal
Align archival information formatting with that of the publisher field, such that it can be stored as:
archive: <string>
or
archive:
name: <string>
location: <string>
and deprecate the archive-location field.
The text was updated successfully, but these errors were encountered:
Issue
Currently, the information about the name and location of an entry's publication and/or archive can be stored in Hayagriva. However, the archive and publisher fields do not store data in the same way.
Publisher
Information regarding an entry's publisher can be stored either as a name:
or as an object with separate keys for its name and location:
Archive
Yet archival information is stored in a flat structure:
Proposal
Align archival information formatting with that of the publisher field, such that it can be stored as:
or
and deprecate the
archive-location
field.The text was updated successfully, but these errors were encountered: