home.social

#registrar — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #registrar, aggregated by home.social.

fetched live
  1. Trump's AI rebrand causes 'unprecedented' demand for Slovenian website names

    by Laura Cress / via BBC

    ✍️ 22 x times more domain registrations this month 🙂 Wish you a nice weekend !

    #AI #trend #tech #registrar #web #domain

    bbc.com/news/articles/cqx2z23x

  2. @[email protected] @[email protected] @loops

    Does #loops support tor access? What is the onion address of loops.video?

    Disclosure statement: i publish #antifa content at loops.

    The #Registrar of the .video top level domain is "Identity Digital" an USA based company.

    ht tps://loops.video/v/h-6atgLHIi

    #TLD #domesticTerrorism #autistiInventati #Fwdiverse #Tor #hiddenService

  3. Anyone else able to access, help.sav.com/ ?

    I'm trying to contact support, because it still shows renewal for my two domains at the $244/year price 😔 even though, some are reporting that it should be the $25/year since I had that price before they were acquired by Sav.com

    #Sav #Cloudflare #Registrar

  4. Hello les gens. Il me reste encore un domaine hebergé chez Gandi. Là ils me sortent genre 40euro/an alors que c'est un simple .net, du coup, il est temps de le faire gérer par un autre organisme.

    Vous pouvez me confirmer qu'Infomaniak, c'est le bon plan pour le transférer ? j'ai deja un compte chez eux.

    #domain #registrar #infomaniak #gandi

  5. I've received some phishing emails today, from the domain ojv.sk, purporting to be from Porkbun. I've reported them to Porkbun via their abuse reporting form:

    https://porkbun.com/abuse

    #porkbun #registrar #email #phishing

    porkbun.com | Abuse Complaint

  6. I've received some phishing emails today, from the domain ojv.sk, purporting to be from Porkbun. I've reported them to Porkbun via their abuse reporting form:

    porkbun.com/abuse

    #porkbun #registrar #email #phishing

  7. Some services will be momentarily down today while we migrate from Dynadot to Dreamhost for our domain Registrar. Moving forward, all DNS will be managed at Hurricane Electric and/or Dreamhost. Thanks for patience 🙏🏼

    This sudden change was due to Dynadot changing their subdomain record policy from 250 to 50 without notice. This caused a week-long disruption in building out new services due to any record over the cap being irrecoverable once deleted and new ones being impossible to create. Despite having 150+ records in the past, Dynadot responded that they've never supported more than 150 and would only restore that.

    Both the change in terms and contract without notice and the dishonesty once a ticket was filed serve as sufficient reasons to ditch Dynadot. This was surprising to say the least. They've been a solid Registrar. As for DNS, we only used it the last three years having originally used afraid.org for over a decade. Ultimately, this is for the best however, because it is always unwise to keep one's DNS and Registrar at the same host. Hurricane Electric's DNS is additionally a breath of fresh air from 1998-2002 era and so easy to use - the alphabetical rendering of records amazing 🤩

    It's always DNS !!

    #DNS #selfhosted #linux #debian #registrar #sysadmin

  8. I've officially began my #indieweb journey! Have I started writing? Nope. Have I built my site? Negatron. So what the hell have I accomplished?

    Well... I focused on who gets my money and code first. It sure as shit ain't gonna be US #BigTech.

    I have shut down my US based domain #registrar and #VPS and moved over to #EU alternatives that are supporting #digitalsovereignty.

    I'm looking forward to this journey :)

  9. @karlauerbach @tychotithonus

    Cavebear wrote:

    I have trouble accepting anything rooted in a country code top level domain (ccTLD), such as .me or .it, as being secure for use identifying people in the US.

    Notwithstanding contemporary community constructs such as KeyOxide, there is an air of (perhaps misplaced) stability with some popular ccTLDs, like, .CA or .CO and even with some that aren't (arguably) quite so deserving, like .TV which has itself had a few turbulent hiccups for registrants in the past. The .CA ccTLD has seen it's fair share of Californian's attempting to capitalize on the mnemonics of that ccTLD, when clearly, this isn't something Canada is happy about, and indeed, one might argue that it dilutes the national branding that is beneficial to Canadian companies.

    .CO is right up there near the top of the warning bells, since many believe that governments have both total authority over their ISO-3166 assets and the wisdom to manage them - they do not.

    In an even earlier article penned by Kieren McCarthy, he states:

    >The first thing .CO Internet did was to ignore accepted wisdom. Even now, many of those comfortable with the status quo claim that new extensions are “not needed”. They include well-known Internet figures such as Tim Berners-Lee, inventor of the World Wide Web. According to this logic, the Internet’s naming infrastructure is no more interesting than the phone system or the road network.

    For my part, even back when offered tidy little sums to provide "professional valuations" for various domain names, I typically accepted the contract and disappointed the client by providing my expert assessments of $35.00 - NSI was charging $70.00 for two year registrations at the time.

    Easy Peasy. The value of a domain registration is, within reason, that which the registry operator sets as the registration fee.

    So with respect to Mr. McCarthy's observation, I concur with the belief that these machinations we rolled out in the 1980's as vehicles to assist humans in mapping out and arriving at particular IP addresses are certainly, nothing more than what could be arbitrary strings in a database, assigned (i.e., registered) by request to someone who will leverage it for utilitarian purposes. I know that's really dry. It's how any engineer would look at such a construct functionally.

    Where things got weird was when people with marketing minds started to claim a piece of the pie, when it wasn't even sliced into pieces:

    - You cannot own a domain name. It's a registration, congruent with the nature of a phone number - pay the renewal fee or that string of characters will return to the pool of available names.
    - You can't assign value beyond that of the registration fees established by the registry
    - If you built a brand of value tied to your (phone number or) domain registration's string, and that registration expires, the value of that brand reverts to $0.00 - once again, you cannot own a domain name, or a phone number!
    - If you build a brand and register that service or trademark with the USPTO, know that it by definition exists separately from a domain registration that you do not, and cannot yourself, own.
    - If you trust your brand on the two letter ccTLDs of nations, know that your brand's name recognition is subject to the whims of that nation and maybe even that nation's ever shifting political sand beneath it.

    That last one is interesting when you consider that even the United States' management of the .US Top-Level Domain came under public scrutiny for the resulting calamity when the rug was pulled out from long time regional registry providers and their registrants when the geographic nature of 3LD registrations and below under the .US ccTLD were sunsetted under the management of the NTIA.

    To be fair, this wasn't nearly as catastrophic as the zillions of registrants whose domain registrations were amputated following Brexit.

    The .TV ccTLD has been in the news as well, scrutinized as a Top-Level domain that will potentially cease to exist, eventually. and historically, management of .TV's registry operations (and marketing) has been a never ending marathon of musical chairs. GoDaddy is actually the operator, while the Tuvalu Telecommunications Corporation handles all the sales and marketing for the brand.

    Montenegro has had a tumultuous life cycle, and the reservations expressed by Karl aren't just valid, but IMO, should be taken as a literal precautionary note. Nevertheless, pigeonholed schemata persist when the marketing types slick back their hair with Brylcreem and their mouths start moving, with promises of great fortune billowing from their lips. the .ME TLD was born, if you will, from the ashes of a succession of ISO-3166 ccTLDs going back originally to Yugoslavia's .YU ccTLD.

    Although I've been focusing on the ccTLDs that have attempted to brand with varying degrees of success and reliability, the smell of money attracts the same carpetbaggers to gTLDs like .mobi and .tel have had varying degrees of success as registries - with some, like the .GOO TLD outright imploding. Let's cover a few...

    - .TEL - A lot of money was poured into this new age virtual business card that was supposedly only available as captive portal with pre-populated fields to fill out for your contact information. I guess that didn't work out too well, following the initial interest by curios folks, since they've officially done away with that hard requirement. Truth be told, it was always possible to simply register your own DNS servers as AUTH and completely bypass their captive portal system, and many gearheads did just to make light of what many considered redundant, ridiculous, and unnecessarily retro.
    - .WORK - As if it could be the rubber banding of a wagon wheel, instead of the original steel girding that .jobs (and yes, there was a .job application too) never really delivered on, this might go down as a better 'marketed' mousetrap, but I don't get the impression that this TLD is really making many waves, and the utility is rather questionable too for anything other than very specialized cases that might be better served under one of the classic gTLDs.
    - .JOBS - I was personally brought in as an expert consultant in to help get this (and .JOB, which didn't make it) accepted in a round 2 application in 2004, for acceptance into the DNS Root with ICANN, which was successful. But that's only half the battle, when job seekers actively flock to Dice, Indeed, XING, Linkedin, and one considers that the average human will at first likely guess that a site called jobs.com might be a first stop on their career search (retail.jobs forwards to usa.jobs), I don't know if the past 21 years have really bore out any fruit for this particular TLD. I was never enthusiastic about the potential, I mean, consider dog_groomer.jobs, yet I was highly optimistic that I could get them across the finish line of the acceptance process - which I did.
    - .WOLTERSKLUWER - Yes that's called an Easter Egg. I've never heard of a single .wolterskluwer domain, or the TLD itself, but all I can come up with "Egads! What were you thinking?" Oh, yeah, the Easter Egg... .BOO is indeed for real. As you can see below, I checked the availability for Yogi_and_Boo.Boo, at the time of writing at least. No I did not follow through on registering but I'm sure that someone will. I still check however, occasionally, to see if Chicken.Coop is available.

    The DNS Name Space is full of failed TLDS.

    Getting back to having enough confidence in a TLD to base your business product (and as it follows, your "brand"), I'm going to finish this article up with a bit of a horrible potential outcome when you register a domain name in the ccTLD namespace when the government is either politically unstable, inept, or both.

    This is the case of the .BZ ccTLD. the original delegation by Jon (Let's just call him IANA, because that was his pseudonym for many years until his passing) was placed in what one would surmise to be a relatively stable environment - a university.

    This delegation of Authority to the TLD Manager was effected on 03 September 1991 to the University of Belize, in according with the rollout of ISO-3166-1 alpha 2 codes for each country. Nothing to see here folks, so we move along to...

    The phenomenon known as the .com bubble and its contemporary, affectionately or infamously referred to as the Domain Wars, close on the heels of the Browser Wars.

    Whereas the registry for the ccTLD for Belize was from 1991 primarily manually, yet competently administered (i.e., by hand), the Government of Belize saw dollar signs after Jon passed away in October of 1998 and subsequently decided to contract out marketing and registry operations to a firm by the name of Economic Solutions Inc. (ESI) in 1999. That's where I come in.

    History has recorded, out of convenience sake, I suppose, that the contract between the Government of Belize and ESI was for marketing only, but that's not what the contract that ESI provided me said. They were to take over registry operations and do the marketing to compete with the new .BIZ gTLD that the nascent ICANN was going to place in the DNS root.

    Since I was already operating several types of registry operations ESI wanted to contract my firm to merely expand registry operations to include the .BZ ccTLD. This was not a problem, and within a few hours had a standalone registry system operational as a prototype. Since this wasn't going to be a part of any existing registry operations I had at the time, I required money to complete a build out for production commercial operations in my data center.

    This is where things began to get a little sticky, as those jokers at didn't seem to understand that I don't really care about their lofty goals, and neither myself nor my CEO at the time were going to do anything without up front compensation. we provided them with the IP addresses, etc., of the new name servers, but made it clear that this zone was not going live until we were fully funded.

    It devolved into a back and forth between the Government of Belize along with ESI on one side, demanding that ICANN.... um.... IANA, rather, change the delegation in the root, and the University of Belize folks on the other, who were quite nice, amicable people.

    I guess this battle between the government of Belize and "IANA" went on for a couple more years, long after I severed the relationship with ESI for not performing, and eventually, that same claim of non-performance was the basis for Belize to cancel their contract too.

    Anyway, in 2001 the university spawned a new entity, University Management Limited (UML), to manage everything - including the marketing, and it's remained that way ever since. All's well that ends well. But the point is, this isn't what the government wanted, and IANA made it eventually clear that they weren't going to change the delegation for the zone to any other entity. - and this is a good thing, because governments are stupid. The university staff were more than willing to work through a coordinated smooth transition, but ultimately it was ICANN - not the government of Belize, who put their foot down when it came to operational integrity.

    In closing, I'd like to point out the likely damage caused to the approximately 80,000 SLD registrants under the .EU who had their registrations revoked (of the total of more than 300,000 that were threatened), as a result of Brexit, is a good example of what could have happened, had the Government of Belize had their way, on a smaller scale, yes, but with even less regard for their existing registrants.

    And that's how incompetent governments do things when you don't have technical guardrails in place to prevent them from shooting themselves in the foot.

    #tallship #DNS #Registry #Registrar #Domain_Names #IANA #ccTLD

    ⛵

    RE: https://sfba.social/users/karlauerbach/statuses/116953628070701544

  10. Hmmmmm .... these domains are taken ...

    • asdf.net
    • asdfasdf.net
    • asdfasdfasdf.net

    W00t!?!?! 😲

    (I didn't want any of them, was just trying to extract the price from a registrar not having an ordinary price list)

    #internet #domains #registrar

  11. 😱 Oh no! Telegram's precious #t.me #domain got suspended, and now we must sit through a tragic tale of #domain #pricing and #shared #hosting plans! 📉 Who knew a domain #suspension could double as a thrilling infomercial for #registrar services? 💁‍♂️
    whois.com/whois/t.me #Telegram #services #HackerNews #ngated

  12. Is Porkbun 502ing for anyone else?

    I love when my registrar is hosed and I can't admin DNS. Does this count as "It's Always DNS"? Because I think it does. Fucking DNS.

    #ops #devops #infra #dns #registrar #porkbun

  13. Boerse Stuttgart’s Seturion partners Italy’s BlockInvest, Weltix for DLT settlement – Ledger Insights

    Boerse Stuttgart Group’s DLT settlement solution Seturion is partnering with Italian firms Weltix and Real House, the company…
    #Italy #Europe #Europa #EU #blockchain #BlockInvest #BoerseStuttgart #corporateregistry #digitalassets #digitalsecurities #distributedledger #DLT #registrar #securitytokens #settlement #Seturion #tokenization #Weltix
    europesays.com/italy/26045/

  14. 🚀 A WebTuga obteve Acreditação de Registrar junto da Verisign para domínios .COM e .NET

    Fomos acreditados pela Verisign para registo e gestão direta de domínios .COM e .NET, as duas extensões mais registadas do mundo.

    Uma ligação direta ao registry, com mais controlo, eficiência e autonomia.

    +Info: blog.webtuga.pt/webtuga-obtem-

    #domains #dominios #registrar #icann #verisign #registry #accreditedregistrar #webtuga

  15. Recette avec une pincée de @LaurentChemla et un zeste de @pb, grâce à qui notamment, #Gandi était chouette. Avant.

    > Gandi is a good case, because of the many expectations that were betrayed, and the deeper reflection linking to vampire capitalism. Gandi is a textbook example of enshittification, which I think is sad but interesting to talk about.

    **Rise and Fall of Hosting Provider Gandi.net** by @tomgag

    gagliardoni.net/#20260528_gand

    #NDD #Enshittification #Registrar

  16. 🚀 A WebTuga tornou-se oficialmente no primeiro ICANN Accredited Registrar sediado em Portugal.

    Um marco histórico para a empresa e para o setor digital nacional. 🌍

    +Info: blog.webtuga.pt/webtuga-e-a-pr

    #icann #registrar #domains #dominios #webhosting #alojamentoweb

  17. Any experts in domain names here?

    I’m stuck in limbo. My domain left name.com but is not showing up on the new registrar

    The weirdest thing? The Whois is showing PDR Ltd. d/b/a PublicDomainRegistry.com
    But that’s not where I transferred it (I sent it to whc.ca)

    Did name.com fuck up and sent it to the wrong place? How do I get it back?

    #DomainRegistration #registrar #domainregistrar #dns #dnssec #domainregister #domainname

  18. Don't buy the “domain + e-mail” subscription from #Strato.de:

    ➡️ They disallow you to use their mail server (which you pay for!) if you choose to use a third-party name server.

    ➡️ Also, you can't set a custom TTL for your DNS records (at least I found no such option).

    ➡️ Recently, their customer login was unavailable for hours (so it was impossible to modify any DNS settings).

    #domain #domains #registrar

  19. The `.radio` top level domain name will be transferring to a new registrar:

    *"We are writing to inform you that your .radio domain name will be transferred to a new registrar by the beginning of May 2026, on a date that will be shortly notified."*

    #HamRadio #AmateurRadio #hamr #radio #registrar #RadioRegistrar #DNS #Domain #RadioDomain

  20. How to create a free customizable 'mini web-site' at Porkbun with 'Link in Bio' - host your own social links and content:

    kb.porkbun.com/article/234-how

    #porkbun #registrar

  21. @neinoi @burgervege
    Je ne dis pas que c'est le meilleur #registrar, la plupart le permettent.
    Mais c'est un des moins chers.

  22. Anyone has any opinions on netim.com/en as a #DNS #domain #registrar ? They seem to be based in Europe, have both TLDs I'm interested in, and apparently prices lower than I've seen in a bunch of others.

    Edit: other recommendations also welcome.
    #AskFedi #selfhosted #sysadmin

  23. @Matt_Noyes

    I imagine you meant gandi; if it's them, I'd avoid them like the plague - they used to be a great company but got acquired by a fund who promptly and discreetly increased the prices for the sole benefit of their shareholders.

    Personally I switched to porkbun, and if you'd rather avoid US-based services, I hear infomaniak is great too.

    #dns #registrar

  24. I advised gandi.net to some people asking a European domain registrar.
    And HOLY SHIT, I had to renew some domain today, and it is BATSHIT INSANE. Somehow, I wasn't impacted before today.

    So no, gandi sucks ass since they got acquired by Total Webhosting Solutions.

    I'm not going to OVH, because I got many bad experiences with them, directly or told by friends.

    So I'm gonna go to my server hoster which is dedibox/scaleway/online.net. Somehow, I never used them as a registrar, but they do it, so, why not.

    #dns #registrar #domain

  25. On after-hours shifts, as an intern, you get to do more “pure” medicine such as taking a history and doing a physical exam which is largely what you've been training to do throughout your medical degree

    Read more 👉 lttr.ai/AZZN9

    #DoctorHierarchy #DoctorTitles #Intern #Internship #Registrar #Blog #PrincipalHouseOfficer

  26. #FBI orders #domain #registrar to reveal who runs mysterious Archive.is site

    The Federal Bureau of Investigation is trying to unmask the operator of Archive.is, also known as Archive.today, a website that saves snapshots of webpages and is commonly used to bypass news #paywalls.

    arstechnica.com/tech-policy/20

  27. "We are releasing this work in a spirit of #generosity and to encourage others to suggest improvements with the larger goal of providing resources to help the broader #culturalheritage sector think about how to use #machinelearning technologies outside and beyond the promises of the billboards advertising these same technologies in Silicon Valley and the world over."
    #registrar #museums #OpenSource
    millsfield.sfomuseum.org/blog/

  28. We need a new Domain provider at work. Must be developer friendly (an API, a Sandbox etc), support a good range of international TLDs (e.g. uk, .au, and .in), and not be prohibitively expensive. Currently reviewing dnsimple.com/ but would love some alternatives #dns #domain #registrar

  29. What domain registrar do people recommend? I have a .net domain via (#domain.com) which works fine but they did a dick move to my friend and I want to move to somewhere more trustworthy.

  30. I'd like to move away from my US-based registrar and go non-US. I've already got my eyes set on a target but asking here just in case. Requirements:

    ‣ Supports `.cc`
    ‣ Support catch-all email
    ‣ Reasonably priced
    ‣ No cryptobros

    I already perused european-alternatives.eu/categ

  31. Für eine bald zur Verlängerung anstehende und von mir registrierte #Domain verlangt der aktuelle #Registrar einen überdurchschnttlichen #Preis. Daher erwäge ich einen #Transfer.

    Wer kennt sich mit der #Architektur und #Technik dahinter aus und kann mir sagen, wovon es abhängt ob die restliche #Laufzeit bei einem vorzeitigen #Umzug verloren geht oder dieser einfach weitere 365 Tage hinzugerechnet werden? Und ob die Gebühr stets neben der Übertragung auch eine Verlängerung beinhaltet?

    Ich frage mich ob das in irgendeiner Form einheitlich reguliert ist, das mit der konkreten #TLD zu tun und/oder kann das individuell durch die #AGB unterschiedlich gehandhabt werden?
  32. #GandiNet Je déconseille fortement comme #registrar - Déjà les prix se sont envolés et maintenant, les notifications de fin de nom de domaine, c'est 1 jour à l'avance. Ce n'est pas sérieux !

  33. Polling the collective consciousness: what domain registrars seem to be doing a good job today? A client has a couple domains coming up for renewal in November, and I think I'm going to use the occasion as an excuse to get them off one of the evil registrars.

    These folks are a US-based non-profit; they operate their own DNS, email, web hosting, etc. (Well, I help run it for them.) All they need is the domain registration and the ability to point it at their nameservers, no add-ons.

    #domains #registrar

  34. Managing Previously Unmanaged Databases

    This article was written for and first published in the Summer 2025 Newsletter of the  Registrars Committee Western Region: https://rcwr.org/newsletters/ 

    Usually, you find me writing about the real-world messes in our collections. Crammed stores. Decaying garments. Surprise findings in abandoned offices of your predecessor. But today, I want to write about another kind of mess: the information that was recorded – or wasn’t recorded – in your database.

    You don’t have a database? Then, this article will help you prepare for the time you are getting one. It may even help you in deciding what system to chose.

    The Problem

    Sometimes, the mess in your database is even bigger than the mess in your storage. Do any of those sound familiar to you?

    • The same information was entered in different fields, depending on who did it.
    • A lot of records are only partly filled and the information contradicts the paperwork.
    • Some objects have more than one record while others have none.
    • Data is entered inconsistently, so you have “pipe wrench”, “wrench, pipe”, “multigrip pliers”, and “water pump pliers” and they all refer to the same kind of tool.
    • Typos and inconsistent data entry make it impossible to get exact results when you search your database.

    It is tempting to just correct those as you go, while you are working with the objects and I am not saying that this is a bad idea. But if you really want to make progress and getting your database into an overall better state you need a more strategic approach to it.

    The problem: While you are silently fixing all the inconsistent data entries, someone else may be doing the next messy one. You first of all should determine how you want the fields to be used. You might think you have a clear idea about this, but have you, really? And have you put that into written form?

    First Step: What should go where and how?

    Your first step is not about fixing what is in there, it is about making sure that your database is used exactly the way you want it. For that you are creating a document that lists all the fields you have and how you want them to be used.

    Be precise. “A description of the object” for the free text field “Description” will let you end up from vague entries like “Bridal gown” to a two-page description on the history of bridal gowns copied over from Wikipedia. So, formulate how you want your description to be.

    Example: Object Description

    “The first sentence should state what type of object it is, the main color, and important characteristics. Think of it as a way you would describe it to someone who has to look for it in the storage but doesn’t have a photo. This might be followed by a couple of sentences about the characteristics of the individual piece that makes it different from another object of the same type. Think of things like an unusual ornament, a tear, or a large stain. The purpose of this field is to make sure we can identify this individual object without doubt.”

    Also make clear when information doesn’t belong in the “Description” but in other fields in your database, for example:

    “Analysis of the object condition belongs in the “Condition” field. Websites about this type of object belong in the “Web links” field. Mentioning of this object in exhibition catalogs belong in the “Associated Catalogs” field. Mentioning in literature should go into the “Bibliography” field. Remarks on the provenance and previous owners go into the “Object history” field.”

    Example: Terms from Controlled Vocabularies

    If you are using a field where you want the entry to be taken from a controlled vocabulary, for some fields it might be enough to write “pick the correct classification from the drop-down menu”.

    Others might be more complex so you need to add more guidance. “Only use terms from Nomenclature” might be at least accompanied with a link to the website https://page.nomenclature.info/ and a few examples.

    If you want your information to be picked from an even more complex source, for example Getty’s Art & Architecture Thesaurus for the material, a “use only terms from the AAT” by far isn’t enough. “This term is about documenting what the object is made of. Therefore, it should be taken from the ‘materials by composition’ branch of the Materials facet of the AAT.” Provide examples, so, whoever is using your document in the future knows what your idea was and how to do a correct entry.

    Guiding principle: But can I find it?

    Your guiding principle when thinking about how to add your data is how you are going to search for it. This will depend on clean data entry on the one hand but also on which search functionalities your database offers. Wordy entries in free text fields often result in a lot of irrelevant search results. By keeping those entries concise and compartmentalizing information in different fields you can search more precisely – if your database offers the possibility to search for the information in those fields separately.

    So, with all the fields you are writing down, always think about how “future you” will be able to look that information up. It will help a lot with making sure you are not missing something important.

    Second Step: But does it work like that?

    After you have written all that, put yourself to the test. Catalog a few objects. 10-20 objects are a good testing sample. Make sure that they are from a large variety of objects. Documenting 10 plates will get you nowhere. Documenting a plate, a dress, a toy, a tool, a radio, and a taxidermied badger will give you a lot of variety. Your collections policy will help you pick a good sample. All objects that could potentially end up in your collection should be easy to catalog with the guideline you are creating.

    While cataloging, you will notice that you have missed some fields and some aren’t fitting for all cases. Perhaps you need to use different ones. Perhaps you need to add new ones if your database allows for it. Perhaps you just have to specify how to enter information in the same field differently for some object groups.

    Adjust and share

    Make adjustments to your document and/or your database so you can really catalog everything that might come into your collection. Once you are satisfied, share the document, that you might now call a “cataloging guideline” or “documentation help file” with everybody who uses the database, not just those who are doing the cataloging. It will help people who only use the database for searching know where they can find the relevant information.

    But I don’t have a database

    If you don’t have a database yet but just an assortment of excel spreadsheets and/or index cards, writing such a guideline and doing a few tests in an excel spreadsheet that contains the fields you have in mind will help you determine what your new system needs to be capable of. Furthermore, you can use this spreadsheet for documenting your collection now according to your guideline and later you have that data ready to import into your new system.

    Now onward to tackle the mess!

    Once you are at this point you have achieved something amazing: from now on, whatever is cataloged in your database will get a clean, easy to retrieve record. Sometimes, there might be slight adaptions to the guideline necessary, but by and large everybody knows how data should be entered and if you find it isn’t, you do have your document to point them to how it is done correctly. Introducing new colleagues, no matter if paid or volunteers, to cataloging in your institution will get much easier.

    Now you can work on getting the rest of the database in better state.

    What kind of mess do you have?

    Not all messes are created equal. Sometimes the core of the records is okay, they only need some adjustments and corrections here and there. Others are so bad that the only thing you can do is to quarantine those records in an area of your database (for example by moving them to a separate department, marking them with a checkbox, or giving them a special classification like “legacy record”) where you can look them up as a reference but do new, clean records for all your objects.

    Creating new records for old stuff

    If the latter is your case, you now have your guideline to follow through. You might want to check back in your “legacy records” if there is any information you might have missed. Sometimes there are hints to donors you can’t find in the paperwork. Make sure your new record notes this as “according to old record #…” so it is clear where the information comes from and that it probably has to be verified. Some systems allow to link to the old record and it might be a smart idea to do that.

    Improving existing records one step at a time

    If you decide that your existing records aren’t too bad overall, they just need to be corrected here and there, you need to break down this task down into manageable steps. A lot of database messes were created because someone started the work with good intentions but then couldn’t follow through and someone else picked up without any idea what their predecessor did or had in mind.

    Knowing that, you will of course create a document with your database improvement strategy so if you have to leave off for some reason whoever comes after you knows what you did and why you did it.

    Often, it is easiest to focus on one single field and correct that throughout the database than trying to rectify all the fields in one record at once. The repetitiveness of the task helps with speeding it up. For example, take all the tools and make sure their records show the right term in the material thesaurus, usually “metal” or “wood”, sometimes both. Then move on to the household items and do the same. Or stay with the tools, but this time, you are rectifying the classifications, so the “gooseneck chisel”, “chisel, carving”, “gouge”, and “pick” can all be found under “chisel” and get sub-classifications depending on their use or form. In no time you will have become an expert in the different types of chisels, so you get much faster in classifying them.

    Involving Interns and Volunteers

    It is easy to see how some of this work can be delegated to dedicated volunteers or interns. If they have good attention to detail they should be well able to take over some of those corrections. And since they are only correcting one area of an object record in a defined set of objects at a time, the results are much easier to check than if you would have asked them to do a whole new record for an object.

    Do paperwork and database match?

    Just like you went through material and classification, one step will involve going through your paperwork and making sure that everything you have a Deed of Gift for is recorded as gift and everything you have an invoice for is recorded as purchase. Again, you work in steps that make sense, in this case perhaps you go folder by folder or year by year, depending how your files are organized.

    You might end up with a lot of object records you don’t have paperwork for and on the other hand paperwork that doesn’t seem to match anything you find in your storage. Make sure your database has a field for noting that, too. And of course, what should be recorded how in it becomes part fo your cataloging guideline.

    Ultimate Goal: The Treasure Trove

    Your ultimate goal is that your database becomes your reliable friend. If everything else is messy, your database is the place where you have a tidy record that tells you what you know about the object – and sometimes what you don’t know. It will become your point of reference while working on improving your collection in the physical world.

    Angela Kipp

    #CMS #collectionsManagement #CollectionsManagementSystems #data #dataOrganization #database #databases #documentation #registrar

  35. The basic structure of a medical team is, ideally, at least one of each of the following individuals – intern, resident, registrar, and consultant (in order of least to most seniority).

    Read more 👉 lttr.ai/AZZN1

    #DoctorHierarchy #DoctorTitles #Intern #Internship #Registrar #Blog #PrincipalHouseOfficer

  36. What does a jet have to do with managing previously unmanaged collections?

    Photo by Andreas Glöckner via Pixabay

    Simple answer:

    Nothing.

    More complex answer:

    I am in the process of translating the book into German and sometimes there are hiccups. In chapter 4, I talk about the difficulties of enforcing access policies for your storage area. A process which, as we all know, comes with all sorts of difficulties, the problem of taking the key from someone being a humiliating gesture in our Western culture being not the least of it.

    In the English original, there is the sentence:

    “Enforce the access policy with the three ps: persistence, patience, and politeness.”

    Needless to say, such sentences don’t translate well. Usually you just rephrase them and let go of the idea that you can find three words starting with the same letter in the other language. However, I think I did find a way this morning:

    “Halten Sie mit „Drei G“ an Ihren Zugangsbeschränkungen fest: mit Geradlinigkeit, Geduld und Gutem Benehmen.”

    Finding three words starting with the letter G with the same meaning like the original (although the third one is cheating a bit, using two words) was already a big win. But the even bigger win was that this way I now have the double meaning of 3 G in it, alluding to the g-forces in physics.

    I could of course take that analogy and run with it, saying that when we change longstanding processes and habits like we inevitably do when we start improving things in our collections, it means that we accelerate things and take people out of where they are used to go and expecting to go. And as we know from physics, if we accelerate things, a force is applied to the one being accelerated, which can have unpleasant side effects.

    But I don’t want to overburden that little sentence. Instead, just imagine me giggling slightly when you come across it reading the book. 🙂

    Angela

    #AccessControl #collectionsManagement #documentation #museum #MuseumDocumentation #registrar

  37. And so it begins:

    Heise: Wikipedia: Republikaner leiten Untersuchung ein

    Um es in aller Deutlichkeit zu sagen: #Wikipedia kann den Forderungen nicht nachgeben. Wikipedia kann nichteinmal einer einzelnen Forderung zum Schein nachkommen. Wikipedia ist gegen solche staatlichen Eingriffe umfangreich geschützt. Das hat in der Vergangenheit dazu geführt, dass Wikipedia in Russland, China, der Tprkei vollständig grsperrt wurde. In China ist das weiterhin der Fall. Das Problem: Die gesamte Infrastruktur von Wikipedia ist in den USA. Insbesondere die Domains "wikipedia.org", "wikimedia.org, "wikidata.org" und "wmftools.org" werden vom #Registrar der top-level-domain .org bereitgestellt und dieser Registrar befindet sich in den #USA und hat keinen Schutz gegen #Trump.

    Verabschiedet Euch von Wikipedia. Es ist #vorbei.

  38. Welcher #Domain #Registrar empfiehlt sich denn für .de Domains?
    Zwingende Features:
    - Setzen der autoritativen #Nameserver
    - #DNSSEC
    - ≤ 10 €/Jahr netto

    #followerpower

  39. OK, Gandi is shit since they got sold.
    Which DNS registrars are good nowadays?

    #DNS #Gandi #registrar

Share on Mastodon

Enter the server where you have an account.