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

OA Monitor: read ORA binary_files__file_embargo_release_method #60

Open
tomwrobel opened this issue Apr 11, 2019 · 3 comments
Open

OA Monitor: read ORA binary_files__file_embargo_release_method #60

tomwrobel opened this issue Apr 11, 2019 · 3 comments

Comments

@tomwrobel
Copy link
Collaborator

[This issue emerged from the ORA-SE meeting on 11 April 2019]

The current crosswalking does not plan for SE to read file embargo release method from ORA, and there is no straightforward way to import this information into OA Monitor. However, this could be relevant for future development. This issue has therefore been created to discuss the possibility of doing this and to track the development of the feature.

@eugeniobarrio @jjpartridge I'll leave it for you to discuss, please reassign to me once you've found a conclusion :)

@eugeniobarrio
Copy link
Collaborator

so file embargo release method possible values, manual and automatic?

@AndrewBennet
Copy link
Collaborator

If it helps, the Elements data model for files consists of the following properties:

  • Proprietary_ID
  • FileUrl
  • FileUrlAccessibility (Public, Private, Unknown)
  • Filename
  • Extension
  • Size
  • CreatedWhenAtSource
  • MimeType
  • SHA-1 or MD5 Checksum
  • Description
  • EmbargoReleaseDate
  • EmbargoDescription
  • Version

@tomwrobel
Copy link
Collaborator Author

@mrdsaunders @jjpartridge confirming that this is a won't fix until post release? If you want to make sure that the value crosswalks correctly, we could get that done and fix the rest later?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants