-
Notifications
You must be signed in to change notification settings - Fork 483
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
Metadata: general and domain specific Metadata #27
Comments
Original Redmine Comment Metadata for 4.0 Documentation:
|
Original Redmine Comment Moving to QA for hihj level ticket; individual isses should be opened as new tickets. |
Original Redmine Comment Tested on 3/26 Basic blocks fields and features in place with the exception of some open subtasks. Closing ticket |
Updated French translation - Dec. 5th.
Author Name: Gustavo Durand (@scolapasta)
Original Redmine Issue: 3434, https://redmine.hmdc.harvard.edu/issues/3434
Original Date: 2014-01-28
Original Assignee: Kevin Condon
With 4.0 being a rewrite of the code base, this ticket represents one of the core functional components to be done. Individual items that can be tested separately or need to be passed to another developer or designer should be added as new tickets under this one.
In 4.0 we plan to revise how we handle metadata. While we plan to have general metadata which is true of all datasets (title, author, description, topic classification, etc), we will separate out the domain specific metadata (currently for social science fields from ddi), so that the end user can select a domain and not have to worry about fields that are not relevant.
includes:
handling of templates for domains
reimplementing study versions for 4.0
Related issue(s): #65
Redmine related issue(s): 3473
Child issue(s): #37, #38, #45, #71, #73, #76, #78, #79, #81, #83, #85, #140, #258
Redmine child issue(s): 3444, 3445, 3452, 3479, 3481, 3484, 3486, 3487, 3489, 3491, 3494, 3549, 3672
The text was updated successfully, but these errors were encountered: