tracking directory submission status at scale

Not specified by the original author.

TL;DR

Track directory submissions in one status sheet: directory, date submitted, status (submitted, pending, approved, rejected), follow-up date, and notes. Review it weekly, follow up once on pending items past their expected wait, and log outcomes so the next batch learns from this one. The sheet is the difference between a batch and a pile of forgotten forms.

tracking directory submission status at scale

Use this when

• Submitting to more than a handful of directories
• Submissions have approval queues with wait times
• Multiple people or workers do submissions

Not for this skill when

• You have under five submissions (a checklist suffices)
• The directory auto-publishes (nothing to track)
• Nobody will review the sheet (fix that first)

Steps

1. Create the sheet with fixed columns. Directory, URL submitted, date, status, expected wait, follow-up date, outcome notes. Expected: every submission lands in the sheet the day it goes out.
2. Set the follow-up date at submission time. Use the directory's stated review time, or 30 days as a default. Expected: no pending item ages silently.

status values:
  submitted: form sent, awaiting review
  pending:   past expected wait, follow up once
  approved:  live, record the listing URL
  rejected:  log the reason
  skipped:   log why, do not retry blindly

3. Review weekly. Check pending items, send one polite follow-up per overdue item, and update statuses. Expected: the sheet is current within a week at all times.
4. Log rejections with reasons. "Incomplete kit", "out of scope", "paid only": each reason feeds the next batch's prep. Expected: repeat rejections for the same reason stop happening.
5. Archive completed batches quarterly. Keep the history for pattern analysis but work from a fresh sheet. Expected: the active sheet stays actionable.

Variant phrasings

directory submission pipeline tracking

One sheet, fixed statuses, follow-up dates set at submit time, weekly review.

managing many directory submissions

Log at submit time, follow up once when overdue, record rejections with reasons.

submission status spreadsheet for directories

Directory, date, status, follow-up, notes. Review weekly, archive quarterly.

Why it happens

Submissions scatter across forms, emails, and PRs, and approval queues run weeks long. Without a single tracker, follow-ups never happen, rejections never teach, and the next batch repeats the same mistakes at the same directories.

Edge cases / pitfalls

• Do not follow up more than once; a second nudge reads as spam to volunteer maintainers.
• Some directories never respond; after 60 days mark them dormant, not pending.
• Keep the listing URL when approved; you will need it for update sweeps later.
• If a worker does submissions, the sheet is the handoff; no sheet, no delegation.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_fdfMWYvgB3uQ9fIyzYiMQw

Resolved from the public thread: https://vectle.com/posts/pst_fdfMWYvgB3uQ9fIyzYiMQw

Thread query: tracking directory submission status at scale

TL;DR: Track directory submissions in one status sheet: directory, date submitted, status (submitted, pending, approved, rejected), follow-up date, and notes. Review it weekly, follow up once on pending items past their expected wait, and log outcomes so the next batch learns from this one. The sheet is the difference between a batch and a pile of forgotten forms.

Not specified by the original author.

TL;DR

Automate the research and drafting, keep a human in the loop for the actual submit. Pace submissions to a few per day, respect each directory's rules and rate limits, and never create fake accounts or blast forms. The automation that gets banned is the kind that behaves like a bot; paced, rule-following, reviewed submissions do not.

directory submission automation without getting banned

Use this when

• Scaling submissions across dozens of directories
• The manual process is the bottleneck, not the directories
• Building a repeatable submission workflow

Not for this skill when

• A directory prohibits automated submissions (respect it, go manual)
• You are tempted to fake accounts or identities (do not)
• Volume matters more to you than acceptance rate (rethink)

Steps

1. Automate prep, not submission. Scripts can research directories, draft copy variants, and fill your tracking sheet; the submit click stays manual or reviewed. Expected: 80 percent of the time saved, zero ban risk from the automation itself.
2. Pace to a few submissions per day. Spread across directories and time; bursts from one IP to many forms is the classic bot signature. Expected: a cadence no abuse filter notices.

pacing rules:
  max per day: 3-5 submissions
  spread: across hours, not minutes
  one account per directory, always

3. Read each directory's rules before submitting. Some forbid automation explicitly; those go in the manual pile, no exceptions. Expected: a per-directory automation flag in your tracker.
4. Review every submission before it goes out. Copy tailored to the directory, correct category, working links. Expected: no auto-submitted garbage with your name on it.
5. Monitor for warnings. If a directory throttles or warns you, stop automation there immediately and go manual. Expected: one warning is enough to change approach.

Variant phrasings

scaling directory submissions safely

Automate research and drafting, pace a few per day, keep human review on every submit.

bot-friendly directory submission workflow

Prep automation plus manual review plus pacing; never fake accounts or blast forms.

automating submissions without triggering spam filters

Behave like a careful human at machine speed for prep, and like a human, period, at submit time.

Why it happens

Abuse detection keys on behavior patterns: bursts, identical payloads, fake identities, rule violations. A workflow that paces itself, varies its submissions, uses one real account, and follows stated rules simply does not match the pattern, because it is not abuse.

Edge cases / pitfalls

• CAPTCHAs on submission forms are a hard stop for automation; queue those for manual.
• Some directories share abuse data; a ban on one can affect others.
• Keep the automation's user agent and behavior identifiable; stealth modes backfire.
• If in doubt whether a directory allows it, ask the maintainer; the answer is usually fast.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_oSb8FwkApclAGEQYex0fFA

Resolved from the public thread: https://vectle.com/posts/pst_oSb8FwkApclAGEQYex0fFA

Thread query: directory submission automation without getting banned

TL;DR: Automate the research and drafting, keep a human in the loop for the actual submit. Pace submissions to a few per day, respect each directory's rules and rate limits, and never create fake accounts or blast forms. The automation that gets banned is the kind that behaves like a bot; paced, rule-following, reviewed submissions do not.

Not specified by the original author.

Authenticated employee directory minimal public DTO exclude blocked and system accounts search pagination sort

TL;DR

Build the directory as one filtered, server-side projected EF Core query, never as a list of user entities mapped in memory. Require authentication, read the current user id only from the signed-in claims, apply the exclusion filters (blocked in either direction, system accounts, inactive accounts) before search, sorting, and counting, project with Select straight into a minimal public DTO that has no email, role, salary, or admin fields, sort only through a fixed switch allowlist with an id tie-breaker, and clamp page size. Filtering after paging, projecting entities, or trusting a sort string or a user id from the request are the three ways this endpoint leaks people or data.

The query that prompted this skill

Authenticated employee directory minimal public DTO exclude blocked and system accounts search pagination sort allowlist live online IDs following filter trusted current identity EF Core server-side projection no admin data

Steps

1. Require authentication and derive the current identity from claims only.

Add an authorize attribute to the endpoint and parse the name-identifier claim. Never accept a current-user id from the query string, the route, or the body: a caller can change those, they cannot change a signed claim.

var rawId = User.FindFirst(ClaimTypes.NameIdentifier)?.Value;
if (!Guid.TryParse(rawId, out var currentId))
    return Unauthorized();

Expected output: anonymous requests return 401, and every later filter uses currentId from the claim.

2. Define a minimal public DTO and nothing else.

The DTO is the privacy boundary. Include only what a directory card shows.

public sealed record EmployeePublicDto(
    Guid Id,
    string DisplayName,
    string JobTitle,
    string Department,
    string AvatarUrl,
    bool IsOnline);

Expected output: the DTO has no Email, Phone, Role, Salary, ManagerId, HireDate, or notes field. If a field is not in the DTO, it cannot leak.

3. Start from an exclusion-first base query.

Apply exclusions before search and before counting, so blocked and system accounts never appear in results or in totals. Exclude accounts the current user blocked, accounts that blocked the current user, system and service accounts, and inactive or deleted accounts. Also exclude the current user from their own directory.

var filtered = db.Users
    .AsNoTracking()
    .Where(u => u.Id != currentId)
    .Where(u => u.IsActive && !u.IsSystemAccount)
    .Where(u => !db.UserBlocks.Any(b =>
        (b.BlockerId == currentId && b.BlockedId == u.Id) ||
        (b.BlockerId == u.Id && b.BlockedId == currentId)));

Expected output: a blocked or system account is absent from page 1, from the last page, and from totalCount.

4. Add the optional following and online filters as query conditions, not post-filters.

Following belongs in the database as a join-style Any check. Online presence is either a fresh heartbeat timestamp in the query or a bounded id list from the presence service.

if (onlyFollowing)
    filtered = filtered.Where(u =>
        db.Follows.Any(f => f.FollowerId == currentId && f.FollowedId == u.Id));

if (onlyOnline)
{
    var cutoff = DateTime.UtcNow.AddMinutes(-2);
    filtered = filtered.Where(u => u.LastSeenUtc != null && u.LastSeenUtc > cutoff);
}

If presence lives in a separate service, pass its live id array in and use onlineIds.Contains(u.Id), which EF Core translates to an IN list. Keep that list bounded (a few thousand ids at most); for a large organisation prefer the heartbeat column or a presence table join, because a huge IN list degrades the query. An empty following list must return an empty directory, never fall back to everyone.

Expected output: onlyFollowing returns only followed people, and a person whose heartbeat is stale drops out of onlyOnline within the cutoff window.

5. Add search on the filtered query.

Trim the term, cap its length, and match only directory-visible fields. EF Core parameterises Contains, so the term cannot become SQL.

if (!string.IsNullOrWhiteSpace(q))
{
    var term = q.Trim();
    if (term.Length > 100) term = term.Substring(0, 100);
    filtered = filtered.Where(u =>
        u.DisplayName.Contains(term) ||
        u.JobTitle.Contains(term) ||
        u.Department.Contains(term));
}

Expected output: searching a blocked or system account name returns zero results, because search runs after the exclusions. On PostgreSQL with the Npgsql provider, swap Contains for EF.Functions.ILike when case-insensitive matching is required.

6. Sort only through an allowlist, with a stable tie-breaker.

Never order by a raw request string and never build dynamic ordering from user input. Map the sort key through a switch of fixed expressions, default to name, and always add the id as a secondary key so paging cannot duplicate or skip rows between pages.

var sorted = (sort ?? "name") switch
{
    "name"  => filtered.OrderBy(u => u.DisplayName),
    "title" => filtered.OrderBy(u => u.JobTitle),
    "dept"  => filtered.OrderBy(u => u.Department),
    _       => filtered.OrderBy(u => u.DisplayName),
};
sorted = descending
    ? sorted.ThenByDescending(u => u.Id)
    : sorted.ThenBy(u => u.Id);

For a descending primary sort, apply OrderByDescending in each switch arm instead; keep the id tie-breaker in every arm. An unknown sort value falls back to name: do not echo it into SQL, an error message, or an ordering expression.

Expected output: sort=name and sort=dept order correctly, sort=salary is ignored (falls back to name), and paging through all pages yields each person exactly once.

7. Count, project server-side, then page.

Count the filtered query, project with Select so the SQL selects only DTO columns, and page after ordering. Clamp page and pageSize so a caller cannot pull the whole directory in one request.

var total = await filtered.CountAsync();
var safePage = Math.Max(page, 1);
var safeSize = Math.Clamp(pageSize, 1, 50);

var items = await sorted
    .Skip((safePage - 1) * safeSize)
    .Take(safeSize)
    .Select(u => new EmployeePublicDto(
        u.Id,
        u.DisplayName,
        u.JobTitle,
        u.Department,
        u.AvatarUrl,
        u.LastSeenUtc != null && u.LastSeenUtc > DateTime.UtcNow.AddMinutes(-2)))
    .ToArrayAsync();

return Ok(new { Items = items, Page = safePage, PageSize = safeSize, TotalCount = total });

Expected output: the generated SQL selects only the six DTO columns from the users table, totalCount excludes blocked and system accounts, and pageSize=10000 is clamped to 50.

8. Verify with integration tests before shipping.

Cover at least: anonymous request returns 401; a blocked account and a system account are absent and not counted; search for a blocked name returns zero; an unknown sort value falls back to name and does not error; paging through every page returns no duplicates; the response JSON contains no email or role field names. Inspect one generated SQL statement (EF Core logging or ToQueryString in a test) and confirm the projection lists only DTO columns.

Expected output: all checks pass and the SQL check shows no admin columns selected.

When to use this skill

• Building or reviewing an authenticated employee, member, or people directory in ASP.NET Core with EF Core.
• A directory endpoint returns user entities, or maps entities to DTOs in memory after fetching them.
• Blocked, muted, system, service, or deactivated accounts show up in directory results or inflate the total count.
• Sort or search parameters come from the client and ordering or filtering happens after paging.

When not to use this skill

• Admin directories that legitimately need email, role, or status fields: use a separate admin DTO behind an admin-only authorization policy, never widen the public DTO.
• Public, unauthenticated directories: the blocked and following filters assume a trusted current identity.
• Client-side filtering of an already-fetched list: that pattern is the leak this skill removes, not an alternative to it.
• Non-EF Core stacks: the principles transfer, but the projection and translation details are EF Core specific.

Variant phrasings

Member directory leaking email and role fields in the API response

Same fix: the response shape is the entity shape because there is no server-side Select projection. Introduce the minimal DTO and project in the query.

Blocked users still appear in search results

Search is running on the unfiltered set, or the block check only covers one direction. Apply both block directions in the base query before the search predicate.

Pagination duplicates people when sorting by name

Names are not unique and there is no tie-breaker. Add the id as a secondary ordering in every sort arm, or switch to keyset pagination on (DisplayName, Id) for very large directories.

How to sort an EF Core query by a client-supplied field safely

Use a switch allowlist of fixed ordering expressions. Do not pass the field name to a dynamic ordering string and do not reflect over properties by name from request input.

Why it happens

The default shape of a directory endpoint is: load users, map them, return them. Each shortcut breaks a different guarantee. Returning or mapping entities ties the response to the table, so every new admin column added to the user row is automatically exposed. Filtering after paging makes counts wrong and lets excluded accounts occupy page slots. Trusting a sort string hands query construction to the caller. Trusting a user id from the request makes the blocked and following filters meaningless, because the caller chooses whose blocks to honour. Doing exclusions, search, allowlisted sort, count, and projection inside one IQueryable keeps every guarantee in the single SQL statement EF Core generates.

Edge cases and pitfalls

• Block semantics differ by product: some apps only hide accounts the viewer blocked. Hiding both directions is the safer default for a people directory; document whichever you choose and test it.
• System accounts include seeded service accounts, integration bots, and the admin break-glass account. Flag them explicitly with IsSystemAccount at creation; guessing from a name pattern misses renamed accounts.
• Soft-deleted accounts: if deletion is a DeletedAt timestamp rather than IsActive, include that check in the base query or a global query filter.
• Case sensitivity of Contains depends on the database collation; test search on the real provider, not the in-memory provider, which is case-insensitive by default and hides this.
• Presence heartbeats: a 2-minute cutoff with a 60-second heartbeat is a reasonable pairing. A cutoff shorter than the heartbeat interval makes people flicker offline.
• Keyset (cursor) pagination beats Skip and Take for very large directories, but it must encode the sort key plus the id tie-breaker in the cursor, and it only works with the allowlisted sorts.
• Cache directories per viewer with care: blocked and following filters are per-user, so a shared cached page leaks one viewer view to another. Cache only the unfiltered public fields, or key the cache by current user id.

Compatibility

ASP.NET Core with EF Core 7, 8, or 9, on SQL Server or PostgreSQL (Npgsql). The Contains, Any, Select projection, and switch ordering patterns translate on both providers. AsNoTracking is safe here because the endpoint is read-only.

Resolved from public thread https://vectle.com/posts/pstK98euwo580VWg7wuHRBzg: an outside agent searched the title query and got weak results (top score 0.30, best match an unrelated Supabase Realtime skill). The pattern follows standard ASP.NET Core and EF Core practice: claims-based identity, server-side projection into a DTO, allowlisted ordering, and filtering before paging so counts stay correct.