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

Mosaics to reflect Commons categories faithfully when re-importing & updating #82

Open
susannaanas opened this issue Feb 10, 2016 · 4 comments

Comments

@susannaanas
Copy link

When re-importing a mosaic from a Commons-category the files would be added or removed from the mosaic based on categorization on Commons. This is useful when a maps category is needed to be subcategorized into smaller units, i.e. a collection into atlases. In this case they are removed from the top category and placed into a subcategory.

Should manual adding of maps to mosaics then be possible?

This will require marking various files that are included in a maps category to be tagged differently: an index, explanatory notes, title page etc. -> a separate issue? Should it happen on Commons or Warper? How would the data be imported from and updated on Commons? Requires changes in the Map template.

@timwaters
Copy link

I think a map should belong to many mosaics, many collections, just like they can belong to many categories. Maps in the wikimaps warper currently can belong to many categories.

For example "maps of the world" "maps of UK" "maps of Yorkshire" "maps of Leeds" "maps of 19C yorkshire", "maps made by Mr Smith" "BL maps" etc. 1 map, many categories. 1 map, many mosaics.

Regarding types of "map" the warper currently has 3 types.
"Map"
"Not a map"
"index / overview"

Currently, an admin can:
Delete a map
Remove a map from a mosaic
Set it's type.

Additionally, right now, an admin in the warper can set a mosaic to "not visible" for these larger categories or collections where a mosaic makes no sense. I think that users should not have to change Commons Categories to fit the warper.

Of these only maps specfied as "map" type can be shown in a mosaic. Others are treated as images and do no harm in being imported.

Imports only happen by advanced users - those users should also be aware that all images in a category will be imported.

@timwaters
Copy link

I think therefore that this enhancement would be to ensure that if a category is imported and any maps within it are no longer in the category, for these maps to be removed (but not deleted) from the relevant mosaic.

@susannaanas
Copy link
Author

I agree. Let me elaborate

  • Maps in Wikimedia Commons may also belong to several categories. It is good that it can also happen in the Warper.
  • I think we should create a connection from the map template to the Warper re: types. There is a property in the Map template "Map type". It has not been utilized. The purpose has been to be able to express the types, such as "street map", "topographic map", "sea chart". We could use that or we could create a new property (I prefer a new property). The values could be read from Commons in the import, updated in the Warper, and updated to Commons when there is an update event, such as warping.

The advantage of syncing would be that when a GLAM uploads 1000 maps of which 250 are descriptive pages, they could be tagged already in the upload.

@timwaters
Copy link

Okay I've created #83 "Import from commons should read map type from template & handle accordingly." for handling types from the template upon addition

This issue will be for categories re-importing / updating.

@timwaters timwaters changed the title Mosaics to reflect Commons categories faithfully Mosaics to reflect Commons categories faithfully when re-importing & updating Feb 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants