107 Matching Annotations
  1. Mar 2024
  2. Feb 2024
    1. "http://creativecommons.org/public-domain/",

      I suggested dropping, but making 2 notes.

      1. The canonical URI should be http://creativecommons.org/publicdomain/zero/1.0/. It is what is dereferenceable with content negotiation (for example, see Easy RDF converter https://www.easyrdf.org/converter) and with the API: https://api.creativecommons.org/rest/1.5/details?license-uri=http://creativecommons.org/publicdomain/zero/1.0/
      2. I think the Presentation 3 validator might have a validation problem as it seems to only accept URIs from Creative Commons that starts with http://creativecommons.org/licenses/ even thought I think the above should be perfectly valid.
    2. Related Recipes

      What about:

    3. "summary": { "en": [ "Excerpt from a performance of Egba Iyawo recorded in Kabba Division, Kwara State. " ] }, "rights": "http://creativecommons.org/public-domain/", "requiredStatement": { "label": { "en": [ "Attribution" ] }, "value": { "en": [ "<a href='https://www.ui.edu.ng/'>www.ui.edu.ng</a>; <a href='https://www.ibadan-ias.org/'>www.ibadan-ias.org</a>; <a href='mailto: unibadanias60@gmail.com'>unibadanias60@gmail.com</a>" ] } }, "metadata": [ { "label": { "en": [ "Producer" ] }, "value": { "en": [ "Institute of African Studies, University of Ibadan" ] } }, { "label": { "en": [ "Date" ] }, "value": { "en": [ "1980–1990" ] } }, { "label": { "en": [ "Collection" ] }, "value": { "en": [ "<a href='https://iasibadanarchive.com/'>Archive of Sound and Vision, Institute of African Studies, University of Ibadan</a>" ] } } ],

      Drop?

    4. Understanding that not all file formats are playable in all viewers or, as relevant, all browsers, the viewer is expected to present for playing the first audio file it is capable of playing.

      For implementers, should we state here how a viewer should make this determination? For instance, the value of format of the Sound resource?

    5. In this recipe, on the other hand, the resources differ in format and therefore can differ for viewer capability; consequently, the choice belongs both to the viewer and to the user.

      On the other hand, in this recipe, the resources vary in format, which can affect viewer's ability to play the file. As a result, the decision is shared between the viewer and the user.

    6. In the Image Choice recipe, there is no format difference in the images and therefore no capability difference for the viewer; the choice belongs to the manifest creator and the user.

      In the Image Choice recipe, as there are no format variations among the images, the viewer experiences no difference in capabilities. The choice belongs only to the manifest creator and the user.

    7. For an audio resource, you want to provide viewers or other software readers with multiple formats or qualities so the appropriate and/or compatible one can be presented to the listener.

      You have an audio resource in multiple file formats or sound qualities and you want to allow a viewer or other software component the ability to present the most appropriate file to the listener.

  3. Sep 2023
    1. Ms. Boles couldhave researched a bit further on the motivational tools and incentives being used atother law schools as a takeaway or chart in the article or delved more deeply into thepsychological literature on incentivization or motivational approaches in law schools orhigher education
    2. Her scholarly agenda also is cutting edge in a post-pandemic worldthat needs more attention given to the technological innovations in legal practice andthe quickly transitioning areas of AI in the landscape of legal research, technologicalcompetence for lawyers, evolution of law practice management, and technologytraining programs in law schools

      Good thing to mention in report

    3. 20th volume

      When will this be released? What does forthcoming mean in the Law Library?

    4. Continuing Legal Education

      7 continuing education things

    5. Scholarly Publications

      2 publications, 1 forthcoming

    6. orthcoming

      Is this okay?

    7. Ibelieve the absence of adequate technology training to prepare practice-ready lawyers is something thatmany law schools are currently encountering, and a problem that will surely grow as technologies likeartificial intelligence become a larger part of the successful practice of law. My planned scholarly agendamoving forward will continue to look for ways to improve technology training programs at law schools, inparticular those who do not have the budget or workforce necessary to implement major changes toinstitutional structures.

      Clearly thinking about scholarship after tenure and promotion

    8. earned my students’ trust and empowered them

      teaching evidence

    1. If, again, you admit that you have received much pleasure, it is your duty not to complain of that part which you have lost, but to return thanks for that which you have enjoyed.

      If you admit to having derived great pleasures, your duty is not to complain about what has been taken away but to be thankful for what you have been given;

    2. As it is, you have altogether run into the other extreme, and, forgetting the better aspects of your lot, look only upon its worse side: you pay no attention to the pleasure you have had in your son's society and your joyful meetings with him, the sweet caresses of his babyhood, the progress of his education: you fix all your attention upon that last scene of all: and to this, as though it were not shocking enough, you add every horror you can.

      You do not turn your thoughts to the pleasant occasions when you met your son and shared his company, or to his boyish and loving endearments, or to the ways in which his studies advanced: you insist on remembering only that final appearance of Fortune; to this, as though it were not quite horrible enough in itself, you add as much horror as you can muster.

  4. Jun 2023
    1. For a IIIF resource, you would like to add a simple annotation to the resource, where the area of the resource you would like to highlight is not a rectangle.

      What about:

      For a IIIF resource, you would like to add a simple annotation where the area you would like to highlight is not a rectangle.

  5. Apr 2023
    1. Sole Source – Non-Competitive Justification (NCJ) If you can’t find what you need through one of those processes described above and you feel that only one source can provide this, you must justify why this item can’t be bid by submitting an NCJ.  The NCJ requires a very detailed and thorough explanation as to why a bid is not possible and it requires approval by Procurement Services and the campus CBO.  The NCJ form can be found in the forms section of this website. Contracts: Departments seeking to justify a sole-source purchase associated with a contract must complete the NCJ form and type in “see attached NCJ” in the “no bid explanation” field in the University’s Contract Management System. Requisitions/Purchase Orders: Departments must attach the NCJ form in the Market Place Requisition System and choose “sole source” as the order type. *NCJ forms must be filled out completely and signed before attaching to the requisition or contract.
  6. Mar 2023
  7. Feb 2023
    1. platform to Next.js.

      Why?

    2. interoperable ability to build from any Collection following IIIF Presentation API 2.0 or 3.0 specifications

      the ability to build an interoperable site from any IIIF Collection following IIIF Presentation API 2.0 and 3.0 specifications.

    3. Clover IIIF

      link

    4. A heavily

      The original Canopy featured ...

    5. use

      reuse

    6. lunr.js

      link

    7. IIIF Collection

      a single IIIF Collection

    8. as a platform to deliver materials

      the static site generator to deliver materials?

    9. Gatsby.js

      link

    10. to reference IIIF resources hosted externally without any duplication of the source material

      to allow IIIF resources hosted in another repository to be enhanced and remixed without any duplication of the source material.

    11. initial project

      the project

    12. key

      primary

    13. Rising from the Ashes: The Chimney Tops 2 Wildfires Oral History Project
    14. digital humanities website

      what about just "web application"

    15. Basic Features

      Above this, I think the About from index should come over.

      Canopy IIIF is a purely IIIF sourced site generator using Next.js. Canopy is an experimental application that will standup a browseable and searchable digital collections style site entirely from a IIIF Collection and the resources it references.

  8. Oct 2022
  9. Sep 2022
    1. However, if one uses aiohttp, one chooses asynchronous programming, a paradigm that makes the opposite trade-off: more verbosity for better performance

      In asynchronous programming, more verbosity is a trade off for better performance.

    1. “wellbeing initiatives are often constrained by the boundaries of an office, and don't extend to remote workers

      another initiative that fails to impact remote workers

    2. mismatches between individuals and their job or work environment, specifically along the lines of the six areas of work life: workload, control, rewards, community, fairness and values”

      factors that contribute to burn out

    3. “satisfaction, trust, commitment, and control mutuality”

      positive relational indicators

    4. Workplace engagement is often seen as the opposite of burnout

      engagement vs. burn out

    1. View in Annona

      Does this work in Annona? I get this error when I try to load:

      Unable to open [object Object]: Error loading image at https://preview.iiif.io/cookbook/0299-region/recipe/0299-region/body/b1/full/max/0/default.jpg

      But this is strange because the jpg that is trying to be dereferenced isn't in the manifest that is getting passed to the viewer:

      https://preview.iiif.io/cookbook/0299-region/recipe/0299-region/manifest.json

    2. As mentioned above, there are other methods of drawing attention to a region of a IIIF resource:

      In order to keep the "Implementation Notes" section as simple as possible, have we ever considered having a separate section in a recipe for "Other Approaches" or something like that. I think the information here is important and definitely has an audience, but I'm wondering if could fit better somewhere else in the recipe.

    3. describes the region in a region property.

      described in a region property.

  10. Aug 2022
    1. Declarative Programming Languages focus on on describing what should be computed - and avoid mentioning how that computation should be performed. In practice this means avoiding expressions of control flow: loops and conditional statements are removed and replaced with higher level constructs that describe the logic of what needs to be computed.

      Definition of declarative programming

    1. For aggregation or transfer: ZIP, RAR, tar, 7z with no encryption, password or other protection mechanisms.

      ZIP, RAR, tar, and 7z compression formats with no encryption or password protection is acceptable for aggregating (harvesting) or transferring data between systems. This document does not suggest these formats are acceptable for long term storage.

    1. Knowledge of Apache and Nginx servers.

      Do they have opinions about these things? Are they simply aware?

    1. “Using this system we realized very early on that it didn’t have all the answers and we needed to upskill staff to be able to use this system.” Another preservation specialist added, “Searching for a turnkey system is a panacea, no system will do the full-life cycle of digital preservation for you,” and commented, “Everyone is trying to hook up several tools and systems together.”

      this is rarely understood

    2. The difficulty associated with trying to align different systems is compounded, if not actually caused, by the organizational structure of most libraries, which usually separates collections from technology and digital asset functions.

      this

    1. Decision¶ The dcterms:subject property was selected. Example record - cDanielCartoon:455. <genre authority="lcsh" valueURI="http://id.loc.gov/authorities/subjects/sh85040974">Editorial cartoons</genre> @prefix edm: <http://www.europeana.eu/schemas/edm/> . <https://example.org/object/1> edm:hasType <http://id.loc.gov/authorities/subjects/sh85040974> . and archivision:1754. <genre authority="lcsh" valueURI="http://id.loc.gov/authorities/subjects/sh85139020">Twentieth century</genre> @prefix edm: <http://www.europeana.eu/schemas/edm/> . <https://example.org/object/1> edm:hasType <http://id.loc.gov/authorities/subjects/sh85040974> .

      The Decision section is littered with errors.

      Edit: This is addressed.

    2. mods/subject[not(@valueURI)]/name[not(valueURI)]/namePart[not(valueURI)]

      This XPath is wrong.

      Edit: This is addressed.

    3. <form authority="http://vocab.getty.edu/aat/300046300">photographs</form>

      This is not correct.

      Edit: This is addressed.

    4. name

      Unless I'm missing it, this doesn't explain what to do with a name with no roleTerms. Does it get kept, does it get dropped? If kept, is it a "Contributor" or something else?

    5. Level 2

      Is there a reason why we need level 2? What parts of edtf do I need to build in?

    6. As part of leveraging the EDTF format, some conversion will be necessary; e.g. translating date strings to EDTF values as in the following example.

      I'm not sure I see the conversion that this is suggesting. Can someone explain that?

    7. <dateIssued encoding="edtf" keyDate="yes" qualifier="approximate">1948</dateIssued>

      So is this suggesting that we only pay attention to qualifier to determine if something needs to be converted to edtf, otherwise it's a string?

    8. <https://example.org/objects/1> dcterms:created "approximately between 1940 and 1950", "1940~/1950"

      So machine actionable dates and string dates are in the same field?

    9. <dateCreated>approximately between 1940 and 1950</dateCreated>

      So if it is not w3cdtf we just copy it over. Is that right?

    10. <dateCreated qualifier="inferred">1955</dateCreated>

      I assume this means that anything inferred needs to have a tilde (~) concatenated to the end.

    11. If it has more than one abstract like 1001:1, we will still map to dcterms:abstract.

      This contradicts our MAP.

    12. identifier[@type="pid"]

      If not present in MODS, should we always add the pid to the metadata to remember where something used to be?

    13. relatedItem[@type=”otherVersion”]

      What is the expectation for this for migration?

    14. genre[not(@*) and not(string() = ('cartographic','notated music'))]

      Can this be expressed as:

      mods:genre[not(@*) and not(text()='cartographic') and not(text()='notated music')]

    15. dcterms

      What do we mean by dcterms text value?

    16. Decision¶ The dcterms:subject property was selected. Example record - archivision:404 .. code-block:: xml <genre authority=”aat” valueURI=”http://vocab.getty.edu/aat/300021140”>Renaissance</genre>

      This needs to be cleaned up.

    17. dcterms text value

      What does "dcterms text value" mean in this context? Do we mean "LOC Resource Types Text Value"?

    18. relators:rps <http://id.loc.gov/authorities/names/no2001080757> ;

      Is there an expectation for migration that I figure out what the URI should be when I only have a string for non-UTK things?

    19. @type='catalog'‘s value, if present, will be represented by the opaque:sheetmusic_hostItem property.

      This is not in the MAP currently.

    20. Incorrect Value Established Era Term Contemporary United States (1968-present). Era 10 - Contemporary United States (1968 to the present) Postwar United States (1945-1970). Era 9 - Postwar United States (1945-1970’s) The Great Depression and World War II (1929-1945). Era 8 - The Great Depression and World War II (1929-1945) The Emergence of Modern America (1890-1930). Era 7 - The Emergence of Modern America (1890-1930) The Development of the Industrial United States (1870-1900). Era 6 - The Development of the Industrial United States (1870-1900) Expansion and Reform (1801-1861). Era 4 - Expansion and Reform (1801-1861) Revolution and the New Nation (1754-1820). Era 3 -Revolution and the New Nation (1754-1820) Colonization and Settlement (1585-1763). Era 2 - Colonization and Settlement (1585-1763) @prefix dcterms: <http://purl.org/dc/terms/> . <https://example.org/objects/1> dcterms:temporal "Era 4 - Expansion and Reform (1801-1861)" . Example of @displayLabel=”Tennessee Social Studies K-12 Eras in American History” - volvoices:1833. <subject displayLabel="Tennessee Social Studies K-12 Eras in American History"> <temporal>Era 9 - Postwar United States (1945-1970's)</temporal> </subject> These will simply be treated as other subject/temporal values are. Note that we only have strings for subject/temporal values. @prefix dcterms: <http://purl.org/dc/terms/> . <https://example.org/objects/1> dcterms:temporal "Era 9 - Postwar United States (1945-1970's)"

      Not currently implemented in Exodus.

    21. http://sws.geonames.org/4050810

      For Geonames, I think we should always use a content-negotiable URI that matches a graph. For geonames, that would be either the one with the trailing slash or the one about the graph with the trailing slash:

      https://sws.geonames.org/3608932/ https://sws.geonames.org/3608932/about.rdf

      I also think we always want the one with just the trailing slash. Do we agree? Also, I think this can easily be implemented in migration tooling by taking a GeoNames URI and chopping off the about and making sure there is a trailing slash. exodus currently chops the about, but doesn't add the trailing slash:

      https://github.com/markpbaggett/exodus/blob/main/exodus/exodus.py#L203

    22. relators:pub

      This is not a thing, but I'm not sure if it's relators:pup or relators:pbl.

  11. Jul 2022
  12. Jun 2022
    1. rdfs:label "Intermediate File for Interview with Andrea Ludden, 2017-02-06"

      This label is bad.

    2. :sample-audio-range-part1 a pcdmworks:Range ; rdfs:label "Part 1"; pcdm:hasMember :sample-audo-multi-fileset-part1 . :sample-audio-range-part2 a pcdmworks:Range ; rdfs:label "Part 2"; pcdm:hasMember :sample-audo-multi-fileset-part2 .

      Do we need a range for these to live inside of?

    3. :sample-audio-multi-original-mods a pcdmworks:Fileset ; rdfs:label "MODS from Islandora - Fileset" ; pcdm:memberOf :sample-audio-multi ; pcdm:hasFile :sample-audio-multi-file-mods-xml .

      Question for the vendor: If a fileset consists of one file, do you need a fileset?

    1. :sample-audio-release a pcdmworks:Fileset ; rdfs:label "Release File for Interview with Andrea Ludden, 2017-02-06" ; pcdm:memberOf :sample-audio ; pcdm:hasFile :sample-release-file .

      Question for the vendor: If a fileset consists of one file, do you need a fileset?

    2. :sample-audio-original-mods a pcdmworks:Fileset ; rdfs:label "MODS from Islandora - Fileset" ; pcdm:memberOf :sample-audio ; pcdm:hasFile :sample-file-mods-xml .

      Question for the vendor: If a fileset consists of one file, do you need a fileset?

    1. the an

      an

    2. Objects in the digital collections at University of Washington Libraries are delivered via CONTENTdm with the image being rendered on initial via NOT being sourced from a IIIF image service.

      ???

    3. where

      were

    1. International Standard Book Numbers are present as identifier values in the Children’s Defense Fund collection. UT currently has a specific Solr field for publication identifiers (ISBNs and ISSNs) so that these identifiers can be displayed and searched for separately: utk_mods_publication_identifier_ms.

      Note: The wikidata equivalents (P957 and p212) split ISBN into 2 separate fields based on whether it is a 10 or 13.

    2. dbo:issn

      dbo:isbn

    3. dbo:issn.

      This should be dbo:isbn.

  13. Apr 2022
    1. "navPlace":
    2. "type": "Annotation",

      Shouldn't the Annotation have an id property:

      From https://iiif.io/api/presentation/3.0/#56-annotation:

      Annotations must have their own HTTP(S) URIs, conveyed in the id property. The JSON-LD description of the Annotation should be returned if the URI is dereferenced, according to the Web Annotation Protocol.

    3. "type": "AnnotationPage"

      Shouldn't the AnnotationPage have an id property:

      From https://iiif.io/api/presentation/3.0/#55-annotation-page:

      An Annotation Page must have an HTTP(S) URI given in id, and may have any of the other properties defined in this specification or the Web Annotation specification. The Annotations are listed in the items property of the Annotation Page.

  14. Mar 2022
  15. Jul 2021
    1. In case of conflict, consider users over authors over implementors over specifiers over theoretical purity. In other words costs or difficulties to the user should be given more weight than costs to authors; which in turn should be given more weight than costs to implementors; which should be given more weight than costs to authors of the spec itself, which should be given more weight than those proposing changes for theoretical reasons alone. Of course, it is preferred to make things better for multiple constituencies at once.

      Priority of Consituencies

    1. In other non-dereferenceable contexts, such as XML Schema, the namespace identifier is still a URI, but this is simply an identifier (i.e. a namespace name). There is no intention that this can or should be dereferenced. There is even a separate attribute, , which may contain a dereferenceable URI that does point to a copy of the schema document.

      In XML, there is no intent for a namespace to be dereferenceable.

  16. Jun 2021
    1. In this case, the objective of the consuming application is to find accurate, machine-readable descriptive information that might be used to build an index, and thus the application should use the IIIF Presentation API seeAlso property to retrieve such a description if available.

      Again, accurate, machine-readable descriptive information should be found in the presentation manifest's seeAlso property.

    2. 3.5.2. Page Algorithm

      This includes instructions on how to a client should process an ActivityStreams CollectionPage.

    3. Activities may be published about content that has access restrictions. Clients must not assume that they will be able to access every resource that is the object of an Activity, and must not assume that it has been deleted if it is inaccessible.

      The client cannot assume that all content is free of access restrictions. Furthermore, it cannot be assumed that a resource has been deleted if it is inaccessible.

    4. The Activities are collected together into pages that together make up the entire set of changes that the publishing system is aware of.

      Activities are collected together into pages like shown in the example below.

    5. Whenever an “Add” Activity is encountered, it is semantically similar to a “Create” Activity in that it is the first time that resource is mentioned in the stream. It is, therefore, expected that if there is an “Add”, then there may not be a “Create” for the same resource occurring before it. Similarly, there will be no more references to the resource after a “Remove” or “Delete”.

      In an aggregation service, a resource cannot have a Create before an Add. If a resource is marked as Removed or Deleted, it can't have any other references to it.

    6. "type": "Update",

      All level 0 have a type of "Update." Level 0 assumes that the list is reindexed to remove references to deleted resources.

    7. This specification does not include a subscription mechanism for enabling change notifications to be pushed to remote systems.

      I assume a previous specification supported a subscription mechanism that could notify a remote system when something had been published, updated, or deleted.

    8. Work that is out of scope of this API includes the recommendation or creation of any descriptive metadata formats, and the recommendation or creation of metadata search APIs or protocols. The diverse domains represented within the IIIF community already have successful standards fulfilling these use cases. Also out of scope is optimization of the transmission of content, for example recommendations about transferring any source media or data between systems

      Things out of scope: recommendation of descriptive metadata formats or the transmission of content. For instance, what would transmission of av look like.

  17. Mar 2021
    1. At the onset of the pandemic, our analysis shows that interactions with our close networks at work increased, while interactions with our distant networks diminished.

      Our circles and networks are shrinking.

    1. t=10,20 # => results in the time interval [10,20) t=,20 # => results in the time interval [0,20) t=10 # => results in the time interval [10,end)

      Note: empty before or after comma results in 0 or end accordingly.