Not in RM7. They are in the order entered. I did something with a SQLite script a few years ago. https://sqlitetoolsf...-citation-sort/
- RootsMagic Forums
- → TomH's Content
There have been 157 items by TomH (Search limited from 25-February 20)
All my images have now been removed from these Rootsmagic forums
No, that is false. It is your site vyger.co.uk where you hosted your images that is gone or suspended. The image links in your posts now forward to http://123-reg-suspe...cbe2c9c456661d6
The only way I can think of is by using SQLite. You would find the duplicate file pointers in MultiMediaTable, record their MediaIDs, delete one record. Then in the MediaLinkTable, find the records with MediaID matching the deleted one and change those to the remaining MediaID.
Within RM, you would have to manually add tags to the media record you want to keep that duplicate the tags for the one you want to get rid of and then 'Remove media' the latter.
A simple SQLite script can readily identify those media items that have been recorded multiple times.
We removed it because we are not advertising a separate Feedback log. Our concern is people will report on a different system and we will not get the reports we need in our tracking system right now.
Since it is a log of the Feedback submitted to the RM Inc tracking system, it should have no effect on what is submitted. So that should not be a concern.
A helpful enhancement to the RM Inc tracking system would be an ID for the Feedback report sent in the confirmation email to the submitter. That could be entered in our independent Log. If that ID was unique to the issue reported, not just the serial number of the report, it would be even better!
For source templates other than the so-called Free Form, RootsMagic uses its own set of custom GEDCOM tags. Free Form uses only the TITL and PAGE tags. When exporting to GEDCOM, RM van export a templated citation to both custom tags and those two standard tags in the same GEDCOM file. For TITL, it exports the sentence generated by the template stripped of all the citation-specific (source details) fields values (and any text dependent thereon); for PAGE it exports the concatenation of all the citation-specific values separated by a semicolon and space character. The result when imported into a program that cannot support RM's customisations can be pretty awful. And there is no way to export to the other standard GEDCOM tags for sources such as PUBL, AUTH,...
I thought I saw a post from Bruce, right before Thanksgiving, perhaps on Wednesday, saying RM8 wouldn't be out this year, but linking a longer (30min) video tour so we could all get a better idea about it. I can't find that post on the blog or in the FB group, and I can't find the video on YouTube. Did I imagine this? What happened? Does anyone know?
Maybe that was a year ago?
That's an obviously useful enhancement and seemingly easy enough to implement. I just did a crude SQLite query to generate the URLs from a RM database that open the "facts" page for the TreeShare linked person on Ancestry. The URL is of the form:
The LinkAncestryTable contains the person's RM Record Number and the values of treenumber and personnumber in a string in the extID column.
The query I used parsed extID as it appeared in my database and may not suit all:
SELECT rmID , 'https://www.ancestry.ca/family-tree/person/tree/'||SUBSTR(extID,-9)||'/person/'||SUBSTR(extID,1,12) AS URL FROM LinkAncestryTable WHERE LinkType=0;
Have any of you not tried the groups.io successor to the old RootsMagic-Users mailing list? It is independent of RM Inc. https://groups.io/g/RootsMagic-Users/
The two new features:
- Reusable citations
- Customised citation sentences
appear to be quite useful developments. They open up possibilities but maybe some traps.
While a customised citation sentence can be reverted to machine-generated from the citation editor, what happens to it if editing is done to the values in the master source and citation fields or in the source template? If the custom override prevents any of that rippling through, is there any warning about the customised citations that were unaffected by those edits?
Another trap may be needing to transfer a number of reuses (instances?) of a given citation to a different (existing or new) citation. Is the only course of action a delete and create anew?
Another observation: I noticed a Name citation (yeay, exposed as promised) but did not see where it was tagged in the Edit Person window. The primary name shows beside the "Person" label just as in RM7, to which "General" citations are tagged.
But is there a find/replace option within citations? Or out in SQLlite land?
Within RM, the Find Everywhere (sic) tool might give you results with the search term "http" but "Everywhere" is an overstatement.
SQLite can search more broadly than RM has seen fit to implement, seeSearch – Find Almost Everywhere
I retested Groups to duplicate the DB corruption, monitoring the SQLite GroupTable & LabelTable, and Sidebar display contents.
I confidently agree with TomH there are two distinct s/w problems:
1) When you create 2+ empty groups at once, then populate them afterwards, in the same Manage Groups session, those groups are corrupt, specifically they all share the same list.
Further odd display behavior ensues to confuse a user.
There are likely other combinations with empty groups that cause this problem, I will leave that to RM.
2) The Sidebar display does not refresh after adding a person to a group.
You are to be commended for your thorough testing and reporting. You should be a Beta Tester for RM8 and maybe that would ensure that these two bugs are eliminated in it!
One is the original post about not refreshing as it should, an issue not only for Quick Groups but also for some other areas.
A second one introduced by GJohn is corruption of a group or groups by a certain user procedure. Is this not now known to be caused by creating a group with no members (and possibly by deleting all the members)?
They are separate issues.
"Sync" is not even in the RM vocabulary except for it being "Sync Certified" by FamilySearch. TreeShare supports copying an entire RM database to a new Ancestry Member Tree or the reverse, an AMT to a new RM database. That pairing of an RM database and an AMT is a TreeShare connection. From that point forward, changes in one can only be manually updated to the other, one person at a time. There is nothing more to it. It is succinctly described in the Help system under "TreeShare for Ancestry" and in various videos.
Could be a frustration getting it all working. Easier for him if you had a website.