Bartmann Goes Global needs you!

We're collecting examples of Bartmann jugs found around the world. Share your jug with us today and help transform our understanding of this iconic jug's global cultural and historical importance.

Please complete the form below with as much information as you can. FAQs are linked in each section of the form to help you.

If you would like to share a jug with the project but don't want it published on the website, click here to send us the information by email instead.

Fields marked with an asterisk (*) must be completed before submitting the form.

Section 1: Images

Please add up to three images (photographs, drawings etc.)
Format: Images must be .jpg or .png
File Size: Min (123kb) to Max (5mb) in size.

You have added 0 out of 3 allowed Jug images.

One file only.
5 MB limit.
Allowed types: png gif jpg jpeg.

Image type*

Section 2: Where was your jug found?

Please give the location of archaeological excavation or place where the jug was discovered (see FAQ).

Country

Geofield

Section 3: Tell us more about where the jug was found

If relevant, all information about archaeological context goes here (see FAQ).

Was the jug found in an archaeological context?

Tell us more about where it was found. Please select all that apply.


If known, please give the approximate start and end date for the site’s use

Section 4: When was the jug made?

(see FAQ).


If you have an approximate date for when the jug was made, please select it below:

Section 5: Jug type and measurements

Click each box below to select the jug shape, facemask and medallion which look most like your jug. (see FAQ).

Measurements

Please enter the measurements for your jug in millimetres (mm):

Section 6: Additional information

Please add any further information (i.e. unusual features) about the jug below. If your jug has any written inscriptions, please use the ‘inscription’ box to document these. (see FAQ).

Section 7: Curation and publications

Where is your jug held?


If the jug features in any publications, please enter them below

Your Information

Please provide us with this basic information about yourself. We may contact you if we have any questions about your submission.

Click here to confirm you agree to our privacy policy. Please take time to read our Privacy Policy which explains what data we collect and why, how we use it and other information relevant to the privacy of your data.
You can not change the Publish status.

Configure the meta tags below.

Use tokens to avoid redundant meta data and search engine penalization. For example, a 'keyword' value of "example" will be shown on all content using this configuration, whereas using the [node:field_keywords] automatically inserts the "keywords" values from the current entity (node, term, etc).

Browse available tokens.
Basic tags
Simple meta tags.
The text to display in the title bar of a visitor's web browser when they view this page. This meta tag may also be used as the title of the page when a visitor bookmarks or favorites this page, or as the page title in a search engine result. It is common to append '[site:name]' to the end of this, so the site's name is automatically added. It is recommended that the title is no greater than 55 - 65 characters long, including spaces.
A brief and concise summary of the page's content that is a maximum of 160 characters in length. The description meta tag may be used by search engines to display a snippet about the page in search results.
A brief and concise summary of the page's content, preferably 150 characters or less. Where as the description meta tag may be used by search engines to display a snippet about the page in search results, the abstract tag may be used to archive a summary about the page. This meta tag is no longer supported by major search engines.
A comma-separated list of keywords about the page. This meta tag is no longer supported by most search engines.
Advanced
Meta tags that might not be needed by many sites.
A location's two-letter international country code, with an optional two-letter region, e.g. 'US-NH' for New Hampshire in the USA.
Geo-spatial information in 'latitude, longitude' format, e.g. '50.167958, -97.133185'; see Wikipedia for details.
Geo-spatial information in 'latitude; longitude' format, e.g. '50.167958; -97.133185'; see Wikipedia for details.
A location's formal name.

Robots

Provides search engines with specific directions for what to do when this page is indexed.

Use a number character as a textual snippet for this search result. "0" equals "nosnippet". "-1" will let the search engine decide the most effective length.
Use a maximum of number seconds as a video snippet for videos on this page in search results. "0" will use a static a image. "-1" means there is no limit.
Set the maximum size of an image preview for this page in a search results.
Do not show this page in search results after the specified date
A link to the preferred page location or URL of the content of this page, to help eliminate duplicate content penalties from search engines.
A brief URL, often created by a URL shortening service.
DEPRECATED. Used to define this page's language code. May be the two letter language code, e.g. "de" for German, or the two letter code with a dash and the two letter ISO country code, e.g. "de-AT" for German in Austria. Still used by Bing.
Used for paginated content by providing URL with rel='prev' link.
A comma-separated list of keywords about the page. This meta tag is used as an indicator in Google News.
Used for paginated content by providing URL with rel='next' link.
Highlight standout journalism on the web, especially for breaking news; used as an indicator in Google News. Warning: Don't abuse it, to be used a maximum of 7 times per calendar week!
Used to indicate the URL that broke the story, and can link to either an internal URL or an external source. If the full URL is not known it is acceptable to use a partial URL or just the domain name.
Describes the name and version number of the software or publishing tool used to create the page.
An image associated with this page, for use as a thumbnail in social networks and other services. This will be able to extract the URL from an image field if the field is configured properly.
Define the author of a page.
Used to rate content for audience appropriateness. This tag has little known influence on search engine rankings, but can be used by browsers, browser extensions, and apps. The most common options are general, mature, restricted, 14 years, safe for kids. If you follow the RTA Documentation you should enter RTA-5042-1996-1400-1577-RTA
Indicate to search engines and other page scrapers whether or not links should be followed. See the W3C specifications for further details. Note: this serves the same purpose as the HTTP header by the same name.
Sets a cookie on the visitor's browser. Can be in either NAME=VALUE format, or a more verbose format including the path and expiration date; see the link for full details on the syntax.
This meta tag communicates with Google. There are currently two directives supported: 'nositelinkssearchbox' to not to show the sitelinks search box, and 'notranslate' to ask Google not to offer a translation of the page. Both options may be added, just separate them with a comma. See meta tags that Google understands for further details.
The number of seconds to wait before refreshing the page. May also force redirect to another page using the format '5; url=https://example.com/', which would be triggered after five seconds.
Details about intellectual property, such as copyright or trademarks; does not automatically protect the site's content or intellectual property.
Tell search engines when to index the page again. Very few search engines support this tag, it is more useful to use an XML Sitemap file.
Used to control whether a browser caches a specific page locally. Not commonly used. Should be used in conjunction with the Pragma meta tag.
Control when the browser's internal cache of the current page should expire. The date must to be an RFC-1123-compliant date string that is represented in Greenwich Mean Time (GMT), e.g. 'Thu, 01 Sep 2016 00:12:56 GMT'. Set to '0' to stop the page being cached entirely.
Used to control whether a browser caches a specific page locally. Not commonly used. Should be used in conjunction with the Cache-Control meta tag.
Open Graph
The Open Graph meta tags are used to control how Facebook, Pinterest, LinkedIn and other social networking sites interpret the site's content.

The Facebook Sharing Debugger lets you preview how your content will look when it's shared to Facebook and debug any issues with your Open Graph tags.
The word that appears before the content's title in a sentence. The default ignores this value, the 'Automatic' value should be sufficient if this is actually needed.
A human-readable name for the site, e.g., IMDb.
The type of the content, e.g., movie.
Preferred page location or URL to help eliminate duplicate content for search engines, e.g., https://www.imdb.com/title/tt0117500/.
The title of the content, e.g., The Rock.
A one to two sentence description of the content.
The URL of an image which should represent the content. The image must be at least 200 x 200 pixels in size; 600 x 316 pixels is a recommended minimum size, and for best results use an image least 1200 x 630 pixels in size. Supports PNG, JPEG and GIF formats. Should not be used if og:image:url is used. Note: if multiple images are added many services (e.g. Facebook) will default to the largest image, not specifically the first one. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly.
The URL of an video which should represent the content. For best results use a source that is at least 1200 x 630 pixels in size, but at least 600 x 316 pixels is a recommended minimum. Object types supported include video.episode, video.movie, video.other, and video.tv_show. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
A alternative version of og:image and has exactly the same requirements; only one needs to be used. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly.
The secure URL (HTTPS) of an video which should represent the content. Any URLs which start with "http://" will be converted to "https://".
The secure URL (HTTPS) of an image which should represent the content. The image must be at least 200 x 200 pixels in size; 600 x 316 pixels is a recommended minimum size, and for best results use an image least 1200 x 630 pixels in size. Supports PNG, JPEG and GIF formats. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly. Any URLs which start with "http://" will be converted to "https://".
The type of image referenced above. Should be either 'image/gif' for a GIF image, 'image/jpeg' for a JPG/JPEG image, or 'image/png' for a PNG image. Note: there should be one value for each image, and having more than there are images may cause problems.
The type of video referenced above. Should be either video.episode, video.movie, video.other, and video.tv_show. Note: there should be one value for each video, and having more than there are videos may cause problems.
The height of the above video(s). Note: if both the unsecured and secured videos are provided, they should both be the same size.
The width of the above image(s). Note: if both the unsecured and secured images are provided, they should both be the same size.
The height of the above image(s). Note: if both the unsecured and secured images are provided, they should both be the same size.
The height of the above video(s). Note: if both the unsecured and secured videos are provided, they should both be the same size.
A description of what is in the image, not a caption. If the page specifies an og:image it should specify og:image:alt.
The length of the video in seconds
The date this content was last modified, with an optional time value. Needs to be in ISO 8601 format. Can be the same as the 'Article modification date' tag.
URLs to related content
The locale these tags are marked up in, must be in the format language_TERRITORY. Default is 'en_US'.
Other locales this content is available in, must be in the format language_TERRITORY, e.g. 'fr_FR'. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Links an article to an author's Facebook profile, should be either URLs to the author's profile page or their Facebook profile IDs. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Links an article to a publisher's Facebook page.
The primary section of this website the content belongs to.
Appropriate keywords for this content. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The date this content was published on, with an optional time value. Needs to be in ISO 8601 format.
The date this content was last modified, with an optional time value. Needs to be in ISO 8601 format.
The date this content will expire, with an optional time value. Needs to be in ISO 8601 format.
Links a book to an author's Facebook profile, should be either URLs to the author's profile page or their Facebook profile IDs. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The Book's ISBN
The date the book was released.
Appropriate keywords for this content. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The URL to an audio file that complements this object.
The secure URL to an audio file that complements this object. All 'http://' URLs will automatically be converted to 'https://'. Any URLs which start with "http://" will be converted to "https://".
The MIME type of the audio file. Examples include 'application/mp3' for an MP3 file.
The first name of the person who's Profile page this is.
The person's last name.
Any of Facebook's gender values should be allowed, the initial two being 'male' and 'female'.
Links to the Facebook profiles for actor(s) that appear in the video. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
A pseudonym / alias of this person.
The roles of the actor(s). Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Links to the Facebook profiles for director(s) that worked on the video. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The TV show this series belongs to.
The date the video was released.
Tag words associated with this video. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Links to the Facebook profiles for scriptwriter(s) for the video. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Twitter Cards
A set of meta tags specially for controlling the summaries displayed when content is shared on Twitter.
Notes:
  • no other fields are required for a Summary card
  • Photo card requires the 'image' field
  • Media player card requires the 'title', 'description', 'media player URL', 'media player width', 'media player height' and 'image' fields,
  • Summary Card with Large Image card requires the 'Summary' field and the 'image' field,
  • Gallery Card requires all the 'Gallery Image' fields,
  • App Card requires the 'iPhone app ID' field, the 'iPad app ID' field and the 'Google Play app ID' field,
  • Product Card requires the 'description' field, the 'image' field, the 'Label 1' field, the 'Data 1' field, the 'Label 2' field and the 'Data 2' field.
The @username for the website, which will be displayed in the Card's footer; must include the @ symbol.
A description that concisely summarizes the content of the page, as appropriate for presentation within a Tweet. Do not re-use the title text as the description, or use this field to describe the general services provided by the website. The string will be truncated, by Twitter, at the word to 200 characters.
The page's title, which should be concise; it will be truncated at 70 characters by Twitter. This field is required unless this the 'type' field is set to 'photo'.
The numerical Twitter account ID for the website, which will be displayed in the Card's footer.
The @username for the content creator / author for this page, including the @ symbol.
The numerical Twitter account ID for the content creator / author for this page.
By default Twitter tracks visitors when a tweet is embedded on a page using the official APIs. Setting this to 'on' will stop Twitter from tracking visitors.
The permalink / canonical URL of the current page.
The URL to a unique image representing the content of the page. Do not use a generic image such as your website logo, author photo, or other image that spans multiple pages. Images larger than 120x120px will be resized and cropped square based on longest dimension. Images smaller than 60x60px will not be shown. If the 'type' is set to Photo then the image must be at least 280x150px. This will be able to extract the URL from an image field if the field is configured properly.
The width of the image being linked to, in pixels.
The alternative text of the image being linked to. Limited to 420 characters.
The height of the image being linked to, in pixels.
A URL to the image representing the first photo in your gallery. This will be able to extract the URL from an image field if the field is configured properly.
A URL to the image representing the second photo in your gallery. This will be able to extract the URL from an image field if the field is configured properly.
A URL to the image representing the third photo in your gallery. This will be able to extract the URL from an image field if the field is configured properly.
A URL to the image representing the fourth photo in your gallery. This will be able to extract the URL from an image field if the field is configured properly.
If your application is not available in the US App Store, you must set this value to the two-letter country code for the App Store that contains your application.
The name of the iPhone app.
String value, should be the numeric representation of your iPhone app's ID in the App Store.
The iPhone app's custom URL scheme (must include "://" after the scheme name).
The name of the iPad app.
String value, should be the numeric representation of your iPad app's ID in the App Store.
The iPad app's custom URL scheme (must include "://" after the scheme name).
The name of the app in the Google Play app store.
Your app ID in the Google Play Store (i.e. "com.android.app").
The Google Play app's custom URL scheme (must include "://" after the scheme name).
The full URL for loading a media player, specifically an iframe for an embedded video rather than the URL to a page that contains a player. Required when using the Player Card type.
The width of the media player iframe, in pixels. Required when using the Player Card type.
The height of the media player iframe, in pixels. Required when using the Player Card type.
The full URL for an MP4 video (h.264) or audio (AAC) stream, takes precedence over the other media player field.
The MIME type for the media contained in the stream URL, as defined by RFC 4337.
This field expects a string, and you can specify values for labels such as price, items in stock, sizes, etc.
This field expects a string, and allows you to specify the types of data you want to offer (price, country, etc.).
This field expects a string, and you can specify values for labels such as price, items in stock, sizes, etc.
This field expects a string, and allows you to specify the types of data you want to offer (price, country, etc.).

Privacy Policy

  • The moment you submit your Bartmann Jug, you agree to our privacy policy. 

  • All images and data submitted through this form except “your information” will be visible on the object page and can be viewed by other website visitors.  

  • Data from “Your details” will be stored in an internal contact list. This list will not be shared with third party holders. We may use this to contact you if we have further questions about your submission. After the project is finished, this data will be deleted.

  • We will not share your data with any third party providers. 

  • Data given by you except “your information” will also be stored on our project database. This database is used for project research, and therefore the information you submit here may be used in future publications. 

  • If you do not want the information you have submitted to be used, or want parts of your submission or your whole submission deleted, please contact bartmann@mola.org.uk

FAQs

Use the following to help you complete the ‘submit a jug’ form. Please fill out as many details as possible. Not all fields may be relevant to your jug.  

You can view previous submissions in the gallery to see the information other people have entered. If you have any questions that aren’t answered below, please contact bartmann@mola.org.uk

Section 1: Upload an image of your jug

You can upload up to three images, including photographs, drawings, and close-ups of the medallion and facemask. 

Please make sure the object is clean and in focus. Please crop out as much as the background as possible and ideally crop to a square outline. 

To enable the best quality, images should be larger than XXXxXXX and smaller than XXMB. 

Images should be jpg, .jpeg or .png. 

The uploaded image will be made publicly available under the CCBY??? License (web link). Please add the image’s copyright information, so it can be correctly attributed.  

If you do not want the image to be available on the website for public reuse, please contact [EMAIL]. 

Section 2: Where was your jug found?

Add the location where the jug was found. You don’t need to add coordinates or addresses for the museum, archive etc. where the jug is now kept.  

To fill in the location, first you need to select a country name from the list, then enter an address (use street name, city and zip / post code). If you don't know the street address (or the site does not have one), please chose an address which is as close as possible, or an address at the centre of the town / city.

For objects from a shipwreck, you can use google maps or similar to find the longitude and latitude as needed. 

If this information is sensitive (for example, this is an ongoing excavation area) please close the form now and instead contact us to submit your jug via email.

 

Section 3: Tell us more about where the jug was found

 

Choose the archaeological context which best matches where the jug was found. If you don’t know the archaeological context, please select “don’t know”. 

Surface Find: if the jug was discovered on the ground, not associated with any specific archaeological feature or context i.e. while mudlarking. 

Archaeological excavation: if the jug was found during archaeological excavations, for example in a pit, ditch, near a wall, or other layer that can be interpreted as part of the site’s history.  

Use the site types to select all the options which are relevant. For example, if the jug was found while mudlarking in London, you would select ‘urban settlement’. 

Examples of site types:  

  • Urban landscape: city such as London, Köln, Amsterdam 

  • Rural landscape: a site in the countryside 

  • Settlement: 
    Village 
    Town 
    City 

  • Military Site:  
    Castle 
    Fort 
    Camp 

  • Eating / Drinking establishment:  
    Inn 
    Tavern 
    Alehouse 

  • Waterfront:  
    Dock 
    Harbor 
    Foreshore 

  • Burial site:  
    Cemetery 
    Tomb 
    Graveyard 

  • Religious site:  
    Monastery 
    Church
    Temple 

You can add any other site types in the box below. Examples of additional contexts: 

  • Latrine / Waste Pit / Well 

  • Colonial or European-influenced site 

You can also use the box to add further information about the site i.e. “found in a building that was known to have burnt down in 1636”. 

Section 4: When was the jug made?

Please provide a general dating range covering a jug's whole life span from production to deposition. If you are unsure, you can select a wider range of dates from the drop-down menu or leave this section blank. 

Dates are sometimes included as part of the medallion design. You can use the further information box below to give more specific date information.

Section 5: Jug type and measurements

Use the selection of 20 different groups of vessels, medallions, and facemask to find those which most closely match your submission. You can view these and match them to your jug by clicking on the boxes in section 5. The below information provides additional context, but matching should be done visually where possible. 

If you don’t have a complete jug, please just select the elements you have. You can also add further information about these elements, there is a section below to add further descriptions.  

Jug types

The jug type comparisons are pictures / drawings taken from the Dutch “Deventer System” typology framework, provided by Sebastiaan Ostkamp and Aleike van de Venne.   

We have grouped vessels here, based on differences of rim, base and belly shape. The pictures and groups are not in chronological order but are grouped by shapes and similarities. Based on this we defined 20 Groups/Images that you can choose from:  

  • Group 1: A shape like Deventer System no.: s2-kan-98. 15ams16 (Amsterdam)   
  • Group 2: A shape like Deventer System no.: s2-kan-39. 01alk4 (Doorsnede)  
  • Group 3: A shape like Deventer System no.: s2-kan-40. 01alk4 (Doorsnede)  
  • Group 4: A shape like Deventer System no.: s2-kan-02. 97alk2  
  • Group 5: A shape like Deventer System no.: s2-kan-48. 02haa5  
  • Group 6: A shape like Deventer System no.: s2-kan-29. 91nijm1  
  • Group 7: A shape like Deventer System no.: s2-kan-58. 05zwo7  
  • Group 8: A shape like Deventer System no.: s2-kan-44. 17enk11  
  • Group 9: A shape like Deventer System no.: s2-kan-41. 01alk4 (Doorsnede)  
  • Group 10: A shape like Deventer System no.: s2-kan-03. 97alk2  
  • Group 11: A shape like Deventer System no.: s2-kan-16. 05dev4  
  • Group 12: A shape like Deventer System no.: s2-kan-35. 07ven2  
  • Group 13: A shape like Deventer System no.: s2-kan-47. 05aks1  
  • Group 14: A shape like Deventer System no.: s2-kan-73. 99sted  
  • Group 15: A shape like Deventer System no.: s2-kan-73. 15nijm7  
  • Group 16: A shape like Deventer System no.: s2-kan-66. 05zwo7  
  • Group 17: A shape like Deventer System no.: s2-kan-13. 14haa11  
  • Group 18: A shape like Deventer System no.: s2-kan-32. 14vla2  
  • Group 19: A shape like Deventer System no.: s2-kan-21_95dha1  
  • Group 20: Others (No picture). Please use this if your jug does not match any of the above shapes. 

Facemask types

The facemask design comparisons are based on different beard styles, face design (including nose and eyes) and mouth shapes. Pictures are provided by the Keramion Frechen, Boijmann van Beuningen Rotterdam, and LandesMuseum Bonn.  

The facemask groups are not in chronological order, like the jug shapes they are grouped by similar features. 

  • Group 1: Crude facemask: triangular nose; small, closed mouth and short beard. Grimacing expression. 
  • Group 2: Crude facemask: hourglass mouth, short nose. short beard with plaited center. Grimacing expression.  
  • Group 3: Crude facemask. Bulbous nose. Hair / beard extending down the side of face. Short closed mouth. Grimacing expression.  
  • Group 4: two padded mouth, raised and divided eyebrows and stylized flowing beard. Kindly expression. 
  • Group 5: Hourglass mouth, short, sometimes square beard. Raised eyebrows. Grimacing expression. 
  • Group 6: Like Group 5 but with equal / mirrored beard. 
  • Group 7: raised eyebrows, closed short mouth. Stylized flowing beard.  
  • Group 8: Hair extending downside of face to stylized flowing beard. Short mouth. Grimacing expression. 
  • Group 9: Hair extending down face and equal / mirrored wavy beard. Short, slightly opened mouth. Grimacing expression.  
  • Group 10: Hair / beard extending down sides of face, short, sometimes squared wavy beard. Hourglass mouth. Grimacing expression. 
  • Group 11: Upturned grinning mouth, hair / beard extending down sides of face, wavy beard. Kindly expression. ‘Brimmed hat’ rim. 
  • Group 12: Hair / beard extending down the side of face and wavy beard. Closed, short mouth. ‘Brimmed hat’ rim. 
  • Group 13: Hair / beard extending downside of face and equal / mirrored wavy beard. Small, closed mouth. ‘Brimmed hat’ rim. 
  • Group 14: Short mouth, wavy and equal / mirrored beard with slightly horizontal strands.  
  • Group 15: Hair extending downside of face; small mouth. Larger wavy and squared beard. ‘Brimmed hat’ rim. 
  • Group 16: Hair / beard down the side of the face. Open mouth, equal / mirrored and wavy beard. ‘Brimmed hat’ like rim. 
  • Group 17: Hair / beard down both sides of face; braided beard. Short, closed mouth. ‘Brimmed hat’ rim. Grimacing expression. 
  • Group 18: Like group 17. Leaves instead of hair.   
  • Group 19: Beard split in two strands. 

Medallion types

Central design

This does not include friezes or panels, palmettes and small rosette stamps. Please use the further information section below to add further detail on such decorations. 

If the jug has more than one medallion, please add details for the central medallion here and use the further information section to describe the others.

We appreciate that this section requires time and effort. The project team can help by adding or adjusting these based on the images you have supplied after submission.  

The main design could include one of the six following elements: 

  1. Coat of Arms: these shields are real heraldic emblems used by noble families. 

  1. A craftworker's brand or imaginary coat of arms: coat of arms that don’t follow the rules of heraldry or aren’t on a shield, or craftworker’s marks.  

  1. Floral: all types of flowers, greenery or plant imagery 

  1. Anthropomorphic: a human head, a complete image of a person or human-like figure.  

  1. Biblical/Religious: images of scenes from the bible or relating to religious topics. 

  1. Miscellaneous: Any type of image that doesn’t fit into the above list. 

Frame types

Choose a frame type that most closely matches your jug. Pictures for both frame and image type are provided by the Keramion Frechen, Boijmann van Beuningen Rotterdam and LandesMuseum Bonn. You can choose from up to eleven different types of frames:  

Frame 1: undecorated (just one simple outline)  

Frame 2: double line (two outlines)  

Frame 3: triangular prongs  

Frame 4: linear prongs  

Frame 5: inscription near or on frame  

Frame 6: dot tape (a dot pattern with wavy or straight lines between)  

Frame 7: floral pattern (any floral designs)  

Frame 8: laurel wreath (known from Caesar)  

Frame 9: undecorated frame but with rhombus inside  

Frame 10: continuous dots (a band of dots)  

Frame 11: other  

Measurements

Height is measured from the bottom to the highest point of the jug. If you submit an incomplete vessel, use the lowest point and the highest point of the sherd. 

  • Max-width measures the widest part of the jug. 
  • Rim diameter is measured at the top part of the jug. Please use the outer part of the rim to measure. 
  • Base diameter is measured at the lowest part of the jug. Please use the outer part of the foot or the flat base to measure. 

Please provide all measurements in millimetres. 

Section 6: Further information

In ‘Inscription’ you can enter any text displayed on the jug. Mostly this will appear on friezes or panels but sometimes inscriptions appear on medallions or other parts of the jug. Please state where on the jug the writing appears. 

Section 7: Curation and publications 

Object reference /  identifying number: please add the identification number / code that a museum, collector, or archaeological service has given to the submitted object. This may include numbers and letters.  

You can share up to two bibliography references for publications. Please only provide the relevant bibliographical data here and do not insert links.