Giters

IQSS / dataverse.harvard.edu

Custom code for dataverse.harvard.edu and an issue tracker for the IQSS Dataverse team's operational work, for better tracking on https://github.com/orgs/IQSS/projects/34

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Metadata: add 3D metadata block to HDV

sbarbosadataverse opened this issue · comments

commented

There is one installation of DV (Sonia will update) using a 3D block that has been previewed by Matt Cook's 3D data group project at Harvard Library.

I think the adoption of this block should include feedback from Matt's group.

commented

2024/03/20

  • Added to project, prioritized, and moved to Needs Sizing at request of @siacus
commented

FYI I connected with Matt Cook on this issue. Waiting to hear back.

commented

Related to #144

commented

see related issue to add 3D viewer to HDV: #256

commented

Can we also add the 3D viewer to the list of external tools? https://guides.dataverse.org/en/latest/admin/external-tools.html#inventory-of-external-tools

This would involve creating an issue and pull request in the main repo, once we know the details of which 3D viewer we plan to use.

commented

Some notes + links concerning 3D-data specific metadata (or "paradata"):

  • Core "Capture" (i.e., production) and "File" (i.e., model) metadata fields, drawn from Harvard Library Imaging Services' 3D metadata gathering (Qulatrics) form and the file-level Morphosource metadata schema:
    • "3D Technique Used" or "Modality" (e.g., photogrammetry, RTI, structured light scanning, tomography, etc.)
    • "Equipment" or "Device(s)" (could include cameras, lenses, proprietary scanners, etc.)
    • "Poly Count" (i.e., detail/resolution)
    • "Viewer Link" (could link out to Sketchfab page, for example)
    • "Processing Software" (e.g., Metashape, RealityCapture, Polycam, etc.,)
commented

Hi all. If you haven't had the chance to yet, please review the guidelines at https://docs.google.com/document/d/1tY5t3gjrIgAGoRxVMWQSCh46fnbSmnFDLQ7aLkNLhJ8 for creating metadata blocks. Accounting for those guidelines early in the design process should help a lot. These guidelines are mentioned on the metadata customization page of Dataverse's Admin Guides. It's a living document of course so we welcome feedback about it.

And in case it's relevant here, when you're thinking about how to group similar fields together, consider keeping the number of any field's subfields to four or fewer. That way we can avoid some of the design issues that have come up, like the one described in #166. I'm considering adding this to the guidelines but haven't gotten around to it.

commented

Thanks for sharing the very helpful guidelines doc link, @jggautier. I do think we can get this schema down to four subfields (by excluding the "Viewer Link" field, given the work being done with the X_ITE (pre)viewer (as per #56) and align the field titles with your text guidelines. What's next, to deploy a custom block in the HL 3D repo?

commented

Thanks @Cook4986.

I think @sbarbosadataverse will know the next steps.

commented

OK, it's not yet clear if the block is ready to be installed in prod. in its current form in the repo. So, it will have to wait at least until next week. Moving it back into "This Sprint" for now.