-
Notifications
You must be signed in to change notification settings - Fork 3
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
implement simple metadata format #7
Comments
Now looking into PBCore http://pbcore.org/ |
@n8fr8 these fields (author, title, createDate (based on file system on the device), description, license (CC etc), location, tags) look good, but we need to add: Country (researcher is located in), Subject (interviewee), researcher (first, last names/pseudonym) - HRW needs the filename to be formatted like this: 2018-10-29_Country_Subject_ResearcherFirstName_LastName |
2018-10-18_USA_kids+love+pumpkins_Nathan_F |
This is now being documented here: https://github.com/OpenArchive/openarchive-android/blob/master/docs/OpenArchiveSpaceCapsuleSpec.md |
We should (perhaps) mirror the bucket format from Internet Archive... maybe even the metadata XML! https://archive.org/download/CanadaEh
|
I wouldn't go so far as to create the thumbnails, too. :-) Regarding the metadata: I think it's totally fine to use our own (JSON?) format. It's just, that we maybe should keep an eye on what metadata item Internet Archive collects and how it matches to what we have and want. |
There is still the question of renaming the files themselves using our new naming convention, or just the they are stored in. In the case of Archive.org, the bucket is named using the title "slug", in the example of "CanadaEh", while the uploaded file(s) retained their original name "canadaehlogo.png". |
Ok, I looked at the doc and sent you a pull request for markdown improvements. Here are my comments/questions:
Why not GPS coordinates? Or only not in the filename? But if we have GPS coordinates in the metadata (which seems very viable to me, e.g. for locations far out in a desert or something), what to put in the filename? Just nothing?
Why a subdirectory for every entry? That seems very uneconomic, since there are only ever going to be 2 files in it, which, when name-sorted, will always stick together. Also, this won't help in matching Internet Archive's buckets.
Shouldn't we use that instead of our own additional file when uploading to IA?
|
3, 4 5. I will think about this more! |
Waiting on you @n8fr8 |
If a media item is flagged in the client UI, then media file (jpg, mp4, etc) and the associated metadata (json) should be uploaded into a subfolder within the current upload batch folder called "flagged". |
Otherwise, what you have implemented now is fine, as long as the .meta.json contains all the fields entered into the app for each item. I will update the spec document. |
I have updated the spec document herE: https://github.com/OpenArchive/openarchive-android/blob/master/docs/OpenArchiveSpaceCapsuleSpec.md |
Implemented as specified. Please note: The flag is named inside the app as "SIGNIFICANT CONTENT" and is used as a tag. That takes shows up in in the That is different than "FLAGGED". |
Change subfolder on NextCloud to read "Significant Content" |
when OA uploads a file over WebDAV, it needs to also include a second file that contains metadata.
For OA Android, we've started by just exporting a JSON file from the fields of the Media model class we use to persist data in the app. These fields map to the user interface form that a user can edit when they add a new media file into OA.
Here is an example:
{"author":"Nathan F.","createDate":"Oct 17, 2018 4:30:01 PM","description":"aren\u0027t they so orange","licenseUrl":"https://creativecommons.org/licenses/by/4.0/","location":"pumpkin patch","mediaHash":[],"mimeType":"image/jpeg","originalFilePath":"content://com.android.providers.media.documents/document/image%3A66971","serverUrl":"https://cloud.guardianproject.info/remote.php/dav/files/n8fr8/OpenArchive/hcd5-kids+love+pumpkins.jpg/jqnr-kids+love+pumpkins.jpg","status":3,"tags":"autumn;;Halloween","title":"kids love pumpkins","id":15}
This clearly has some android specific fields, but the key ones are:
author, title, createDate (based on file system on the device), description, license (CC etc), location, tags
@foundscapes should chime in here, as well, about what we think are the essential fields, if there are more.
As you can see my metadata json is about as simple as can get, and really is meant as a simple way to capture data from OA in an intermediate format.
The text was updated successfully, but these errors were encountered: