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

GREI 5: HDV Task - Indigenous Data Support #170

Open
7 of 12 tasks
cmbz opened this issue Jan 22, 2024 · 12 comments
Open
7 of 12 tasks

GREI 5: HDV Task - Indigenous Data Support #170

cmbz opened this issue Jan 22, 2024 · 12 comments
Assignees
Labels
Dataverse Project Issues related to Dataverse Project software GREI 5 Use Cases Harvard Dataverse Issues related to Harvard Dataverse Repository Project: NIH GREI Tasks related to the NIH GREI project

Comments

@cmbz
Copy link
Contributor

cmbz commented Jan 22, 2024

Overview

  • TK Label Working Group developed an NIH GREI grant proposal to support indigenous data sovereignty. See: IDS SUPPORT AND NIH-GREI GRANT
  • TKLWG is developing a proposed integration with Dataverse with the following goals:
    • Link to and incorporate identified sources for indigenous knowledge representation, such as TKLabels and Notices
    • Curation processes for managing the creation, reading, updating and deleting of metadata (including an data access workflow); and
    • Present curated metadata (e.g. TKLabels and TKNotices) in catalog records
    • Allow external aggregators to harvest this metadata (specifically the IDN Data Catalog, but preferably standardized model that allows for multiple external parties to harvest).

Tasks

Related

Resources

@cmbz cmbz added GREI 5 Use Cases Harvard Dataverse Issues related to Harvard Dataverse Repository Dataverse Project Issues related to Dataverse Project software labels Jan 22, 2024
@cmbz cmbz self-assigned this Jan 22, 2024
@cmbz cmbz mentioned this issue Jan 22, 2024
9 tasks
@cmbz cmbz added the Project: NIH GREI Tasks related to the NIH GREI project label Jan 22, 2024
@cmbz
Copy link
Contributor Author

cmbz commented Apr 16, 2024

Status: April 2024

@sbarbosadataverse
Copy link

Status: May 2024

  • Jim provided responses to the questions on the integration proposal (see resources above) provided by Ramin and Janet
  • Initiated plans to join the TK Labels Service Provider Early Adopter Program - meeting scheduled for June (SB will try to join and invited Laura (Brazil) and Amber (Borealis) to join the meeting

@cmbz
Copy link
Contributor Author

cmbz commented Jul 22, 2024

Status: July 2024

@cmbz
Copy link
Contributor Author

cmbz commented Aug 22, 2024

Status: August 2024

@amberleahey
Copy link

Thanks for adding this into the demo repository. I tested the LC metadata block and field for a dataset and noticed that when I search for term "name" I was able to make a linkage to a record in the LC Hub. May want to think about how to instruct people to use this, perhaps encourage them to visit the LC Hub for more information about registering projects for linkage before adding to Dataverse metadata? After adding, I wasn't able to delete the linkage it just appeared as greyed out once added. After saving, this did appear to retrieve the TK Labels image and name for display in DV Metadata. I couldn't figure out how to enable this field for display in the Terms or the main dataset landing page citation area for appearing alongside other dataset terms such as licenses.
Screen Shot 2024-08-30 at 3 50 48 PM
Screen Shot 2024-08-30 at 4 02 07 PM

@qqmyers
Copy link
Member

qqmyers commented Aug 31, 2024

FYI: While there were more issues than I expected, I've been able to update the Local Contexts script to address the problem of not being able to delete a project, and have made it configurable so test instances can point to the Local Contexts sandbox rather than their production site. I also managed to find a work-around to enable the Local Contexts information to appear on the main dataset page without having to wait for a change in Dataverse core (rather than just far down on the metadata pane).

I've updated https://docs.google.com/document/d/1umSncPhXApNcvstzqMbqIfx87LCB3RqwS69gPCvbDVE/edit?usp=sharing to include instructions on how to deploy the LC capability and to include more information about what has been fixed/improved in the script.

I'll push these changes to github next week and coordinate with @stevenwinship to deploy them to https://demo.dataverse.org .

@qqmyers
Copy link
Member

qqmyers commented Sep 3, 2024

Demo has been updated by doing the following:

  • Updating the LocalContexts External Vocabulary configuration:
    curl -X PUT --upload-file combined-cvoc-conf.9.3.24.json http://localhost:8080/api/admin/settings/:CVocConf
    (/home/rocky/combined-cvoc-conf.9.3.24.json has the same set of fields as the previous setting (from combined-cvoc-conf.json) with the changes for LocalContexts from the https://github.com/gdcc/dataverse-external-vocab-support repo.)

  • Adding display of LocalContexts info above-the-fold on the dataset page:
    curl -X PUT -d "dsDescription,subject,keyword,publication,notesText,LCProjectUrl" http://localhost:8080/api/admin/settings/:CustomDatasetSummaryFields

  • Addition of a published https://demo.dataverse.org/dataverse/LCtests collection for testing.

  • Turned off the LocalContexts metadatablock at the root collection level (mirroring how we expect this to be used - with LocalContexts only used on some child collections).

image

@amberleahey
Copy link

Looks great, I was able to remove the linkage in demo now! I'll check out the new testing collection in demo as well.
Screen Shot 2024-09-12 at 12 03 00 PM
Screen Shot 2024-09-12 at 12 03 06 PM

@qqmyers
Copy link
Member

qqmyers commented Sep 12, 2024

In the call today: Ashley showed us how DOI lookup almost works with their current code and she is going to make some updates in a week or so to allow it to work (two issues: they allow DOIs in multiple fields, but right now only the provider_id field is indexed, and, while they allow free form text, so we could get https://doi.org/10.5072/ABCDEF or doi:10:5072/ABCDEF etc, a search for 10.5072/ABCDEF doesn't work right now because they aren't breaking the strings up when indexing.) It sounds like searching per field will be allowed in v2, and there will be changes in the returned JSON, so we should expect some details to change. We also discussed how a link might be reported to DataCite or in the schema.org export, etc. and Ashley said she'd get us info on the draft recommendation for the DataCite mapping. It sounds like the schema.org mapping discussion is not as far along.

  • I said I would go ahead with the current script to add some accessibility improvements I just made for the ROR and ORCID scripts.
  • Ramin is going to create a PR to add a config change that will make it possible to add an LC Project id via the API.
  • When Ashley's changes are made, we can look at updating how input is done along the lines discussed in the design doc.
  • If getting a DataCite mapping in is a priority (i.e. if we want it in v6.4), we'll need to move very quickly as v6.4 is starting to get frozen (no new work).

@cmbz
Copy link
Contributor Author

cmbz commented Sep 25, 2024

Status: September 2024

@sbarbosadataverse
Copy link

sbarbosadataverse commented Nov 21, 2024

Status: November 2024

  • OSF met with DV team to discuss the implementation of this support
  • The tasks were updated to include a broader retest by the DV community and documentation work for the Guide. An invite to test and input feedback will be added to Zulip and DV Google Group, with a deadline.
  • Consider engaging with the DDI community around Copyright field use in DV

@cmbz
Copy link
Contributor Author

cmbz commented Dec 10, 2024

Status: December 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dataverse Project Issues related to Dataverse Project software GREI 5 Use Cases Harvard Dataverse Issues related to Harvard Dataverse Repository Project: NIH GREI Tasks related to the NIH GREI project
Projects
None yet
Development

No branches or pull requests

4 participants