Dataverse: v3.6 Metadata field Funding Agency(fundAg) not migrating to v4

Created on 30 Aug 2016  Â·  12Comments  Â·  Source: IQSS/dataverse

We are migrating data from v3.6 to 4.x and metadata field fundAg is not importing into v4. I see a TODO: here
Is there any plan to implement that?

Migration Sysadmin

All 12 comments

@scolapasta -- can you take a look at this TODO discovered in ImportDDIServiceBean.java.

I pointed out the TODO to @scolapasta during an SBGrid meeting last week since @bmckinney mentioned the need to store funding agency (as well as how there would ideally be a list of funding agencies to choose from in the GUI).

I just left this comment at https://groups.google.com/d/msg/dataverse-migration-wg/RLvINbxMfkQ/VIYveInRAQAJ but I'll repeat it here:

There are two ways to indicate funders in the Schema.org JSON-LD representation of datasets now that pull request #5169 has been merged (but not yet released): under "Contributor" ("Funder") and "Grant Information" ("Grant Agency").

@bikramj and all - I'm going to close this out as almost all installations have migrated from 3.x and we don't plan to address migration issues since the benefit would be small.

My guess is that from @bikramj 's perspective, he's trying to help @eugene-barsky get http://dvn.library.ubc.ca upgraded from DVN 3 and onto Scholars Portal. He opened #4996 about this. This is the last DVN 3 installation on the map.

Yes, Abacus Dataverse (3.6) is in plans to upgrade to 4.18 as we manage our
40,000 licensed data files on that platform. To be done by the end of the
year. It will not go to Scholars Portal. We have our research data there,
while licensed data on Abacus Dataverse based in UBC.

Does it help?

Eugene

On Fri, 24 Jan 2020 at 05:26, Philip Durbin notifications@github.com
wrote:

My guess is that from @bikramj https://github.com/bikramj 's
perspective, he's trying to help @eugene-barsky
https://github.com/eugene-barsky get http://dvn.library.ubc.ca upgraded
from DVN 3 and onto Scholars Portal. He opened #4996
https://github.com/IQSS/dataverse/issues/4996 about this. This is the
last DVN 3 installation on the map.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IQSS/dataverse/issues/3323?email_source=notifications&email_token=ACTBP6HBWCHRBYSFXDNJ2CLQ7LT7NA5CNFSM4CODUA52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ2YXRI#issuecomment-578128837,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACTBP6DHWJBUUROXJKXOORLQ7LT7NANCNFSM4CODUA5Q
.

@eugene-barsky, is this issue blocking the migration? If not, what else can we do to help with the migration?

Hi @pdurbin @djbrooke from our side we don't need this anymore since we have completed all the migrations we were supposed to do. Thank you for confirming.

Thanks @bikramj. I'll wait to hear from @eugene-barsky before closing it out.

Thank you, Danny, no, not this issue blocking the migration. Feel free to
close this ticket.

I am reaching out to my team here - Paul Lesack and Jeremy Buhler to be in
touch with you to see whether we need any special help with our Dataverse
3.6 migration.

Eugene

On Fri, 24 Jan 2020 at 06:50, Danny Brooke notifications@github.com wrote:

@eugene-barsky https://github.com/eugene-barsky, is this issue blocking
the migration? If not, what else can we do to help with the migration?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IQSS/dataverse/issues/3323?email_source=notifications&email_token=ACTBP6BUIFWF6VZHJ4P3EVDQ7L537A5CNFSM4CODUA52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ3AXJI#issuecomment-578161573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACTBP6DJGZU25PHHI4J3EGLQ7L537ANCNFSM4CODUA5Q
.

Got it, thanks @eugene-barsky. [email protected] or opening specific issues here is fine!

Was this page helpful?
0 / 5 - 0 ratings