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

Batch Import: Support import for custom fields in v3.6 to help GSD import 1200 studies. #567

Closed
eaquigley opened this issue Jul 9, 2014 · 6 comments
Assignees
Labels
Type: Feature a feature request

Comments

@eaquigley
Copy link
Contributor


Author Name: Kevin Condon (@kcondon)
Original Redmine Issue: 3986, https://redmine.hmdc.harvard.edu/issues/3986
Original Date: 2014-05-15
Original Assignee: Leonid Andreev


Requested by Janina from GSD. They're planning to import 1200 studies and want to use custom fields from their template.

Leonid took a quick look and thought it might be simple -we're currently ignoring the notes type="DVN:EXTENDED_METADATA" but wanted someone to tell him it was necessary to do.

@eaquigley eaquigley added this to the Dataverse 3.6: Patch milestone Jul 9, 2014
@pdurbin
Copy link
Member

pdurbin commented Aug 21, 2014

What's the plan for "custom fields" in Dataverse 4.0? The Manage Network Study Templates section of the DVN 3.x User Guide at https://github.com/IQSS/dvn/blob/develop/doc/sphinx/source/dataverse-user-main.rst#manage-network-study-templates says "You may also add your own custom fields."

@posixeleni
Copy link
Contributor

@pdurbin not sure about custom fields in general but for GSD we are building a custom block for them; see #268 since they are heavy users of Dataverse and have a very unique use case (using dataverse for student output(data) from their courses).

@scolapasta @eaquigley what's the plan for anyone else who wants to create just a small handful of custom fields? Would we have a "custom field block"?

@eaquigley
Copy link
Contributor Author

I'm pretty sure we were planning that you have to get in touch with us about having a custom metadata block and we won't be supporting small handfuls of custom fields being created in the UI. @scolapasta agree or disagree?

@posixeleni
Copy link
Contributor

Makes sense to me!

@pdurbin
Copy link
Member

pdurbin commented Aug 21, 2014

See also #833 about custom fields.

@eaquigley
Copy link
Contributor Author

Moved to: IQSS/dvn#5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature a feature request
Projects
None yet
Development

No branches or pull requests

4 participants