diamm / diamm Goto Github PK
View Code? Open in Web Editor NEWThe Digital Image Archive of Medieval Music
Home Page: https://www.diamm.ac.uk
The Digital Image Archive of Medieval Music
Home Page: https://www.diamm.ac.uk
✨ It's shiny. ✨
Images should be organized in folders:
A migration script will need to be written that uses the database to do the organization of the filesystem.
Facet/Filter by:
Sort by:
Currently the information about a particular page range is all transferred within the IIIF manifest. This bulks up the manifest size considerably and increases the download time of the manifest.
It may be more performant to transition this to an on-the-fly lookup for that range that proxies the range handler to Solr to look up the information for a particular page.
I will investigate and report back.
n/t
It's all in place, just need the controls
The Contribution model in models/site/contribution.py
is waiting to be hooked up. People, Organizations, Compositions, and Sources can all have a "contribute an update" function where people can provide updates to records.
These contributions will then be checked by a member of the DIAMM staff and integrated into the record.
Any contribution marked 'completed' by a member of DIAMM staff can then appear in a 'contributions' section of the object in question. There is also a 'summary' field. Thus the contributor's section for a source might have entries like:
John Smith: Spelling corrections for description. DD/MM/YYYY.
Jane Smith: Correction of inventory listing. DD/MM/YYYY.
&tc.
Supercedes #1
It is not possible to capture structured data in the Open Annotation model. A separate service should be used to capture the data.
The custom service can be implemented with a seeAlso
with format type application/json
Make it pretty.
The about menu will be a single large drop-down ("mega dropdown") multi-column menu that will host all the bits of information for the DIAMM organization.
This is what I'm talking about:
http://designmodo.com/demo/css3megamenu/ (hover over 'earnings').
All of the pages there should be editable from the admin interface.
The headings should be:
Content from these pages can be taken from the existing site, http://www.diamm.ac.uk/about/
We may also want to have a description of the website's technical capabilities, etc.
The pages should be written using Markdown, which is already built into the webapp for source descriptions. The Django staticpages
module may prove to be useful for this task.
canvas
and ranges
are being phased out in IIIF.
Make the relationship to people and organizations a GenericForeignKey relationship so that it can point to both types of models.
This is for:
Searches should be saveable and re-loadable.
would the 'Archive' label not more accurately be called 'Library/Archive'? There seem to be as many libraries as archives on your list of locations.
The information about what is on each page is now transferred in the IIIF manifest as a 'structures' block. Inside of this block there is a range that gives the "canvases" (== pages) that a specific composition appears on in that source.
As a user scrolls, the information should appear on the blank space to the left of the image viewer. (See the Cantus Ultimus viewer for a model of how this should work.)
This could be implemented as a Diva plugin so that we can listen to the Diva page changing events.
At the moment CCM and RISM self-refer to their bibliographies with their own system of bibliographical abbreviations. These are in the bibliography table (though in some cases where both catalogues list the same book, we rationalised and used a single abbreviation for a book, so one of the abbreviations will have been replaced with the other). The abbreviations are not currently visible to users. However there are remarks like this in the descriptions: '...with additions ca. 1600-3 (BrayJB)'. This tells the user which bibliographical entry supplied the date. We could:
This is of very minor importance, but might be worth thinking about. At the moment there is just one field for abbreviations (and I use that to connect to source/item/composition records rather than key numbers as abbreviations are easier to remember), so no differentiation between RISM/CCM and newly created abbreviations for new bibliographies.
When loading a page the JavaScript event handlers don't attach until a few seconds later. Figure out why.
Add the description field to the IIIF manifest.
File "/Users/ahankins/Documents/code/git/diamm/diamm/urls.py", line 39, in <module>
from diamm.views.feedback import FeedbackView
ImportError: No module named 'diamm.views.feedback'
The feedback view is imported in urls.py
but has not been committed, which breaks the build. This should be fixed ASAP.
Currently the archive have their 'former' name in their actual name. We should have a field to separate out the 'formerly' part of the name. Also, this name should be indexed for search.
There should be a filter option for only retrieving sources with images attached to them.
See: http://iiif.io/api/presentation/2.1/#range
Use range for image contents.
The programme for the Med-Ren conference in Sheffield has timetabled a short session for three projects to launch their new websites, and includes DIAMM. The date is 6 July at 14.30 BST.
'type_s' key error in the detail view of copyists.
Traceback :
File "/Users/ariellegoldman/Documents/code/diamm/diamm/serializers/website/person.py" in <listcomp>
109. return [PersonSourceCopyistSerializer(o, context={"request": self.context['request']}).data for o in obj.solr_copyist]
Ranges are a better way of doing a page's contents, instead of annotations for each image. The IIIF manifest generation should be modified to fit the new model.
Any 'short title' list of MSS/hselfmarks should include the tag line following the shelf mark (perhaps in brackets or separated by a dash?); this is in the Source Table field , the point being that you don't have to switch to the full MS description to find out what type of source lies behind a shelfmark (e.g. fragment, choirbook, partbook, chant, theory treatise, etc.). The current facet listing was supposed to do this, but the layout meant it was too narrow to accommodate the information.
Allow external contributors for different objects in the DB
Figure out:
The search box should refresh with the query still intact.
Adding display information for each source result so users can see more information before clicking the link
For images that exist with multiple wavelengths, implement http://iiif.io/api/presentation/2.0/#choice-of-alternative-resources
If /manifest
is requested for a source without images, return a helpful message of some form that indicates that this is not possible.
Add a feedback model and form for registered users. Maybe it can be attached to any piece of content by generic foreign key?
Current users can sign in with their old username or e-mail. If the system detects that they were a former user, it will prompt them to update their password.
Figure out: Can this be generalized for all users (new / existing)
Have to figure out how to omit a key from a serialized instance if the value is null.
If a source is set to non-public, the title should still be shown (so that nothing 'disappears' on people)
Given a IIIF Manifest, import it and match it to pages.
Causing a failure in manifest generation
From an e-mail:
"In the new form of the website would it be helpful to be able to select country by alphabet letter at the top (as when one is searching journals on Jstor) rather than having to scroll through the whole lot?"
From @mscuthbert:
This reminds me (if you're up for suggestions yet), I think that the heading of a manuscript page / search result should be in the form "Oxford, Bodleian Library, Canon. Misc. 213" and not "GB-Ob Canon. Misc. 213" and only use RISM sigla for linking when space is at a premium; given that we're using post-1980 RISM sigla now ("GB-Ob Canon. Misc 213" instead of "GB-Ob213") the space savings is far less than it used to be, compared to the clarity (and potentially higher Google search results)
The contrib.flatpages and contrib.sites app entries is missing from INSTALLED_APPS
in the settings.py on the about-menu
branch.
There should be an indication in the search results which sources have images and which sources do not.
It may make a comeback later, but for now we will disable it until we figure out how browse will work in the new site.
Add a setting in the django configuration to control the width of the thumbnails.
Comments from the old site are in the database, we just need to figure out how to bring them over and attach them to the appropriate new user accounts. This will depend on first building a comment function in the new site, which will be filed as a separate issue.
When clicking on a folio number (start or end) the view should switch to the image view. Will probably need to figure out how to do this properly.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.