ukwa / w3act

w3act is an annotation and curation tool for building web archive collections
Apache License 2.0
19 stars 6 forks source link

Hierarchy of Special Collections #48

Closed peterwebster closed 10 years ago

peterwebster commented 10 years ago

The Special Collections taxonomy has a tree relationship, as implemented in Andy's ACT prototype. Please confirm that this has been carried across.

If it has, then it should be presented as such in the UI, in the Target record Metadata tag.

Please note that not all collections have the same number of levels in the taxonomy; they are created bespoke to each collection. @anjackson

rgraf commented 10 years ago

The Special Collections are presented in Target record Metadata tags 'Subject' and 'Subject 2 level'. We know and load from Drupal two levels. If Special Collections will have more levels - additional documentation is required since loading and presentation in Target view/edit page should be explained.

rgraf commented 10 years ago

The current implementation is based on document "UKWA Subject Terms.docs": UKWA Subject Terms

Top Level Subject Second Level Subject

Arts & Humanities Architecture Art and Design Comedy and Humour Dance Family History / Genealogy Film / Cinema Geography History Languages Literature Local History Music News and Contemporary Events Philosophy and Ethics Publishing, Printing and Bookselling Religion Theatre TV and Radio

Business, Economy & Industry Agriculture, Fishing, and Forestry Banking, Insurance, Accountancy and Financial Economics Business Studies and Management Theory Company Web Sites Economic Development, Enterprise and Aid Economics and Economic Theory Employment, Unemployment and Labour Economics Industries Marketing and Market Research Trade, Commerce, and Globalisation Transport and Infrastructure

Education & Research Dictionaries, Encyclopaedias, and Reference Works Further Education Higher Education Libraries, Archives and Museums Lifelong Learning Preschool Education School Education Special Needs Education Vocational Education

Government, Law & Politics Central Government Civil Rights, Pressure Groups, and Trade Unions Crime, Criminology, Police and Prisons Devolved Government Inter-Governmental Agencies International Relations, Diplomacy, and Peace Law and Legal System Local Government Political Parties Politics, Political Theory and Political Systems Public Inquiries

Medicine & Health Alternative Medicine / Complementary Medicine Conditions and Diseases Health Organisations and Services Medicines, Treatments and Therapies Public Health and Safety

Science & Technology Computer Science, Information Technology and Web Technology Engineering Environment Life Sciences Mathematics Physical Sciences Popular Science Zoology, Veterinary Science and Animal Health

Society & Culture Communities Digital Society Food and Drink Social Problems and Welfare Sociology, Anthropology and Population Studies Sports and Recreation Travel & Tourism

peterwebster commented 10 years ago

You're referring to the Subject.

The issue is with the field referred to in the UI as Suggested Collections. This was implemented in Andy's existing ACT version, with a tree structure as described in my ticket text above. @anjackson

rgraf commented 10 years ago

I was confused by linquistic terms since subjects also are special collections and initial issue statement does not mention Suggested Collections. The tree relationship for Suggested Collections has been carried across from ACT and stored in database in "parent" and "parent_all" fields. But it is not clear how to present these relations in a GUI since relations are very complex.

peterwebster commented 10 years ago

I'm sorry there was confusion of terms.

In the first instance, the list of parents should be presented on its own, without the children mixed. This would be a high priority.

Secondly, I suggest you experiment with a prompting solution - users, on selecting a parent value, are prompted with an alert "This collection has subdivisions. Would you like to use these?" and give the user the list of sub-divisions for that collection. @anjackson would that work ?

Do note that each target may belong to many collections, and also to more than one sub-division in each collection.

rgraf commented 10 years ago

I have tested this now and I believe the issue is solved. Please let me know if there are any additional problems associated with this issue.

peterwebster commented 10 years ago

I like this presentation. However, it seems that the nesting is not correct, and options are duplicated. For instance, the option for London SHA Cluster

is shown nested within (in order down the page) (i) Health and Social Care Act > NHS > Strategic Health Authories AND (ii) NHS > Strategic Health Authorities AND (iii) Strategic Health Authorities AND (iv) as a stand-alone option.

Each option should be available only once in the three: in this case, via: Health and Social Care Act > NHS > Strategic Health Authories

rgraf commented 10 years ago

I have corrected the ‘Suggested Collections’ tree so that each option appears only once. I believe the issue is solved. Please let me know if there are any additional problems associated with this issue.

peterwebster commented 10 years ago

Tree display now fine. See https://github.com/ukwa/w3act/issues/95